Ok, I tripped over this from the FreeBSD people. However the issues are the same. How to get contributions in to the image of stable squeak or just bleeding edge squeak?
Thus I'd think as part of our (not that I'm volunteering for this) mandate there should be a position like below.
PS Of course I realize we do have rules ie [ENH] [FIX} etc and we do have someone doing the job, but lets clarify how it works as part of the process.
At 1:41 PM +0930 6/1/01, Greg Lehey wrote:
From: Greg Lehey grog@FreeBSD.org To: developers@FreeBSD.org, FreeBSD Stable Users freebsd-stable@freebsd.org, FreeBSD current users FreeBSD-current@FreeBSD.ORG Subject: The FreeBSD core team needs your help Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/
...
Those of you who have been following the mailing lists will have noticed (or participated in) a thread bemoaning the continued lack of feedback from the core team. That thread is still very active, but one suggestion (made by phk) was to send out a message asking for help getting things done. It's easy to claim that this would work, but first we need to know if anybody would be interested. Here's phk's text:
HELP WANTED
The FreeBSD core team is looking for an assistant to help with tracking and recording the issues being worked by core.
Responsibilities:
When a request or question is sent to core@ you reply with an acknowledgement that it has been received, and nag the core team until it has been decided on and replied to.
It is also your responsibility to prepare a summary of core@'s businnes once per month and after cores approval of the text, to send this to developers@. This summary should be detailed enough to show the committers which core members participate in the core business and which don't.
You will obviously gain insight into the work of and communications of the core team, but apart from the above mentioned summary, this information is of course strictly confidential.
Working hours:
All.
Benefits:
The FreeBSD project has a comprehensive benefits plan which you will take full advantage off. The benefits include: Lots and lots of email. birth control (you wont have time to spend with your SO), sunburn protection (you wont have time to spend away from the computer).
Despite the appearances, this is not an official request for applicants. We just want to know who would be interested in doing such a thankless task, and whether it's worth core's time to discuss the exact terms of reference (does the person get elected, for example, or appointed?). If you're interested, it's your choice whether you copy -developers, though personally I'd prefer if you just replied to core@.
Greg
Ok, I tripped over this from the FreeBSD people. However the issues are the same. How to get contributions in to the image of stable squeak or just bleeding edge squeak?
Absolutely. There are two models: the "benevolent dictator" model, where one person decides at whim and the community reverse engineers the rules from that, and the "committee of judges" model, with a set of rules laid out and multiple people having write access to the repository work through contributions and make their decisions based on the public rules.
I think the latter is more suited to the Squeak Community, iff SqC decides to give up full control (it's quite silent from there at the moment, I hope this means something good's brewing :-)). At the moment, they embody a sort of "benevolent central committee" model...
Hi!
--- John M McIntosh johnmci@smalltalkconsulting.com wrote:
Ok, I tripped over this from the FreeBSD people. However the issues are the same. How to get contributions in to the image of stable squeak or just bleeding edge squeak?
I read what it said and I have a counter-proposal that I think might work:
Install Jitterbug at SqF. It is a lightweight webbased bug reporting system like Bugzilla (but infinitely easier) which very much can be tweaked too (plain c-code, stores stuff as files in filesystem uses cgi-bin just needs Apache) - I have done numerous extensions to it at my customer.
What we have realized at our customer is that it works perfectly well as a multiuser-todo-list too! Whenever ther is a task we just put in there as a "report" and then it is searchable and we get to set responsible developer, priority, status etc. Very, very easy.
If Cees don't have the time we could fire it up at our machine here at Bluefish, try it out and if it works we can move it to SqF later.
regards, G�ra
===== G�ran Hultgren, goran.hultgren@bluefish.se GSM: +46 70 3933950, http://www.bluefish.se "Department of Redundancy department." -- ThinkGeek
__________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
Install Jitterbug at SqF. It is a lightweight webbased bug reporting system like Bugzilla (but infinitely easier) which very much can be tweaked too (plain c-code, stores stuff as files in filesystem uses cgi-bin just needs Apache) - I have done numerous extensions to it at my customer.
Personally, I'm more of the "you've got a hammer (mailing list) and a screwdriver (wiki), that should be enough" persuasion because I've seen projects die horrible deaths through tool bloat. But if you want to setup a proof-of-concept on your box and everyone likes it, I'll be happy to install Jitterbug.
squeakfoundation@lists.squeakfoundation.org
-
cg＠cdegroot.com -
G�ran Hultgren -
John M McIntosh