You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucy.apache.org by "Marvin Humphrey (JIRA)" <ji...@apache.org> on 2011/05/16 05:48:47 UTC
[lucy-issues] [jira] [Created] (LUCY-150) STATUS file TODO list
STATUS file TODO list
---------------------
Key: LUCY-150
URL: https://issues.apache.org/jira/browse/LUCY-150
Project: Lucy
Issue Type: New Feature
Reporter: Marvin Humphrey
Assignee: Marvin Humphrey
Priority: Minor
The Apache HTTPD project uses a file named "STATUS" at the top level of its
repository to manage and coordinate development. Lucy should adopt a similar
convention, particularly to maintain a consensus TODO list -- though we
should use our STATUS file more sparingly, since our issue tracker, wiki, and
dev list already have a lot of project management tasks covered.
Dev list thread: [http://s.apache.org/EcR]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[lucy-issues] [jira] [Updated] (LUCY-150) STATUS file TODO list
Posted by "Marvin Humphrey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCY-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marvin Humphrey updated LUCY-150:
---------------------------------
Attachment: STATUS
Here is an initial STATUS file. It is similar to the HTTPD STATUS file, but
much, much shorter.
* Instead of listing release blocking issues manually inside the STATUS file
like the HTTPD folks, our file points to the issue tracker. It seems to me
that tracking blocking issues is precisely the kind of thing an issue
tracker does well.
* Apparently the HTTPD folks do things like run votes inside that file, which
makes no sense to me -- votes should take place on the dev list (or
the private list, when required).
* Every TODO item has an associated issue tracker URL at which an in-depth
explanation can be found.
* Newcomers are encouraged to browse our TODO issues and then visit the
HowToContribute wiki page. They are not instructed to grep the source for
"TODO", as most of TODO labels in our code base represent difficult
challenges put off for another day and which would probably not work well
as starter tasks.
* The "release history" section has not been included, as it duplicates
information which will be available elsewhere.
* We haven't released a stable fork yet. When the time comes, we'll add a
entry explaining the role of the STATUS file in a stable fork branch.
* No version information is embedded in the file -- so there's no version
information to get out of date.
> STATUS file TODO list
> ---------------------
>
> Key: LUCY-150
> URL: https://issues.apache.org/jira/browse/LUCY-150
> Project: Lucy
> Issue Type: New Feature
> Reporter: Marvin Humphrey
> Assignee: Marvin Humphrey
> Priority: Minor
> Attachments: STATUS
>
>
> The Apache HTTPD project uses a file named "STATUS" at the top level of its
> repository to manage and coordinate development. Lucy should adopt a similar
> convention, particularly to maintain a consensus TODO list -- though we
> should use our STATUS file more sparingly, since our issue tracker, wiki, and
> dev list already have a lot of project management tasks covered.
> Dev list thread: [http://s.apache.org/EcR]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[lucy-issues] [jira] [Resolved] (LUCY-150) STATUS file TODO list
Posted by "Marvin Humphrey (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCY-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marvin Humphrey resolved LUCY-150.
----------------------------------
Resolution: Fixed
> STATUS file TODO list
> ---------------------
>
> Key: LUCY-150
> URL: https://issues.apache.org/jira/browse/LUCY-150
> Project: Lucy
> Issue Type: New Feature
> Reporter: Marvin Humphrey
> Assignee: Marvin Humphrey
> Priority: Minor
> Attachments: STATUS
>
>
> The Apache HTTPD project uses a file named "STATUS" at the top level of its
> repository to manage and coordinate development. Lucy should adopt a similar
> convention, particularly to maintain a consensus TODO list -- though we
> should use our STATUS file more sparingly, since our issue tracker, wiki, and
> dev list already have a lot of project management tasks covered.
> Dev list thread: [http://s.apache.org/EcR]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira