| Lists: | pgsql-jdbc |
|---|
| From: | Uzma Khawaja <softwareenginer1(at)yahoo(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Open Source Process |
| Date: | 2008-02-25 19:04:07 |
| Message-ID: | 38775.36968.qm@web30703.mail.mud.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-jdbc |
Hi,
I am a student and doing a research on open source processes. I would be thankful if some one can answer few simple questions to help me in my research.
1. If someone wants to work on a feature or bug, is he/she required to get permission before working? Is he/she REQUIRED to join the community?
2. What tools do you use to manage the project (to track the progress, assigning tasks, manage the features and bugs, maintaining patches etc).
Regards,
Uzma Hameed
MS(SE) 3/4,
International Islamic University, Islamabad
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Uzma Khawaja <softwareenginer1(at)yahoo(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Open Source Process |
| Date: | 2008-02-26 03:09:43 |
| Message-ID: | Pine.BSO.4.64.0802252159470.16278@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-jdbc |
On Mon, 25 Feb 2008, Uzma Khawaja wrote:
> 1. If someone wants to work on a feature or bug, is he/she required to
> get permission before working? Is he/she REQUIRED to join the community?
Anyone is free to work on any item they desire. It's wise to check in
first for advice and to make sure two people aren't working on the same
item, but nothing is stopping people from working on their own. The
entire concept of "joining the community" is a little vague. There's
nothing to join other than this mailing list and joining the list is open
to all.
> 2. What tools do you use to manage the project (to track the progress,
> assigning tasks, manage the features and bugs, maintaining patches etc).
>
This mailing list is the primary source for all discussion, patch
distribution, review and everything else. We've got a CVS repository [1]
to distribute the code. Recently I've put a lot of the open items into
the gforge trackers [2], but that's really just a summary of previous
mailing list discussions organized in one place rather than an alternate
stream of new information.
[1] http://pgfoundry.org/scm/?group_id=1000224
[2] http://pgfoundry.org/tracker/?group_id=1000224
Kris Jurka