Difference between revisions of "Talk:Project policy"
SamHartman (talk | contribs) (→Submitting a project for review needs work) |
(→Submitting a project for review needs work) |
||
| Line 4: | Line 4: | ||
== Submitting a project for review needs work == |
== Submitting a project for review needs work == |
||
| − | The "Submitting a project for review" section indicates the submitter |
||
| + | let no one else's work evade your eyes... |
||
| − | should: |
||
| − | <pre> |
||
| − | To start the review period : |
||
| − | 1. Replace {{project-early}} with {{project-review|end_of_review_date}} |
||
| + | You don't have to copy it, but how do other opensource entities manage it? Some of them hide this information from the general public on their wiki pages -- does Kerberos want this to appear to non-members? Come to that, I don't see a "membership" aspect to the wiki. That might be how other opensource groups control access to the ability to suggest new projects. |
||
| − | 2. Add {{subst:project-vote}} at the bottom of the project page. |
||
| − | 3. Send mail to krbdev@mit.edu including: |
||
| − | </pre> |
||
| − | |||
| − | But after saving the project page after following steps 1 & 2, this text |
||
| − | appears on the project page: |
||
| − | |||
| − | An announcement has been sent to krbdev@mit.edu starting a review of |
||
| − | this project. That review will conclude on 2008-04-18. |
||
| − | |||
| − | This is confusing as it sounds like step 3 was done automatically by the |
||
| − | wiki. If the wiki is sending out notification automatically (and I |
||
| − | think it should) then step 3 should be removed. |
||
| + | Eclipse puts its info here: [http://www.eclipse.org/projects/dev_process/development_process.php Development Process]; project statuses are listed here:[http://www.eclipse.org/projects/listofprojects.php List of Projects]. |
||
:The Wiki cannot send out mail. The procedure is correct, but the text on the project page assumes that you actually follow the directions and send the mail. --[[User:SamHartman|SamHartman]] 12:08, 4 April 2008 (EDT) |
:The Wiki cannot send out mail. The procedure is correct, but the text on the project page assumes that you actually follow the directions and send the mail. --[[User:SamHartman|SamHartman]] 12:08, 4 April 2008 (EDT) |
||
| − | ::I think the wording of the project-review template needs to be changed to avoid the ambiguity. Something like: |
||
| + | LaTex seems to manage this on [http://www.latex-project.org/code.html Project Development], to which anyone can subscribe. |
||
| − | The project owner should have sent an announcement to krbdev@mit.edu starting a review of |
||
| + | MySQL has a pretty slick site. I didn't delve into it, but their policy might be something like requiring potential developers to pass a certification test. They also have a very nice [http://forums.mysql.com/ form page]. |
||
| − | this project. That review will conclude on 2008-04-18. |
||
| − | :: --[[User:Wfiveash|Will Fiveash]] 12:42, 4 April 2008 (CDT) |
||
| − | :::I think updating the policy to make it clear that you need to send the mail but that the page will say that mail is sent would be good. I think that updating the template will be more confusing than desirable. I'll also update the template docs. --[[User:SamHartman|SamHartman]] 13:51, 4 April 2008 (EDT) |
||
Revision as of 11:09, 10 April 2008
I don't see a link from the project policy on the k5wiki to code change/integration policy. So I do not know if a code review is necessary and what sort of testing is expected.
- There is not a formalized code review policy. Certainly requesting specific code review as part of the community review of a project would be fine. --SamHartman 12:08, 4 April 2008 (EDT)
Submitting a project for review needs work
let no one else's work evade your eyes...
You don't have to copy it, but how do other opensource entities manage it? Some of them hide this information from the general public on their wiki pages -- does Kerberos want this to appear to non-members? Come to that, I don't see a "membership" aspect to the wiki. That might be how other opensource groups control access to the ability to suggest new projects.
Eclipse puts its info here: Development Process; project statuses are listed here:List of Projects.
- The Wiki cannot send out mail. The procedure is correct, but the text on the project page assumes that you actually follow the directions and send the mail. --SamHartman 12:08, 4 April 2008 (EDT)
LaTex seems to manage this on Project Development, to which anyone can subscribe.
MySQL has a pretty slick site. I didn't delve into it, but their policy might be something like requiring potential developers to pass a certification test. They also have a very nice form page.
