PHPEclipse "meeting" minutes for 06-16-08

Despite the array of start times, rather little was said in the
meeting... and pretty much nothing that's not been said already.  One
resolution which had been passed without a vote is that future meeting
notices will include a list of start times respective to local timezones.

As a result, we're appealing to the list members to vote via e-mail
before the end of this week so that the project can move on.  Given that
we currently lack a hard number of active community members, the
majority of each decision will be based on the total number of votes
received from list members.  Votes received after the cut-off time or
from persons not on the phpeclipse-devel@ list will not be counted.

== Voting overview ==
* Votes must be sent via e-mail to *both* [email protected] and 
[email protected], a manual return receipt will be issued from each for 
your confirmation.
* Votes must be received via e-mail by 2359Z this coming Friday, the
20th of June, 2008. (See http://www.timeanddate.com/worldclock/ for your
local offset... *Zulu time is displayed at the bottom of the page*.)
* Votes not marked as either for or against will not count towards the
total for that resolution.
* If you have questions or concerns, please ask in the IRC channel or
via e-mail.
* If you are no longer active in the project or do not intend to be, 
please let us know so that we can be aware of the resources the project 
really has available.

== Pending resolutions == (Per pre-meeting messages and discussion)
# 1. Project constitution. After reading some posts, I feel that the
Debian Constitution would be a good template for us to model ours off
of.  This would include forming "The Committee" of active developers
responsible for the general management of the project.
Vote: For [ ] resolution #1;
Vote: Against [ ] resolution #1;

# 2. spi-inc.org. We have started the process of joining spi-inc.org. We
need to vote for a liaison to spi-inc.org. That is why i thought entry
#1 is important. We need to outline the different positions, and the
length of terms in office.
Vote: For [ ] resolution #2;
Vote: Against [ ] resolution #2;

# 3. Assets that PHPEclipse depends on. There are domain names, servers,
irc administration that only one person controls. We need to either
allow others access to manage these resources, or stop using them.
Granted they can do what they want with the resource, but as PHPEclipse
we will not recognize nor endorse. Granted that above needs to be
decided by the members of the PHPEclipse Developer committee.
Vote: For [ ] resolution #3;
Vote: Against [ ] resolution #3;

# 4. The possibility of defaulting on the implementation of a separate
www website for the project.  For those who missed my outburst in the
channel, please review the logs on
http://echelog.matzon.dk/logs/browse/phpeclipse/1213308000 starting at
[18:57:41] thru [19:13:52].  In summary, I see little point in the
project maintaining multiple web presences, the development of which is
currently stalling release of 1.2.0 and reducing developer enthusiasm.
Vote: For [ ] resolution #4;
Vote: Against [ ] resolution #4;

# 5. Relocating the current SVN and Trac site to hudson.phpeclipse.com.
After almost 24 hours of dev.phpeclipse.com being offline, it's been
made apparent that we need to be in a better position to control and
manage the project's assets.  This resolution would have the SVN repo
and Trac site replicated hourly between multiple hosts, backed-up in
multiple locations and make DNS control accessible to the members of
"The Committee" in resolution #1.
Vote: For [ ] resolution #5;
Vote: Against [ ] resolution #5;

Thank you in advance for both your participation in the PHPEclipse 
project and this referendum... the future is very promising!

Cheers,

Mike - aka mbowie.


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php