Menu
▾
▴
rexxtill-tasks — RexxTill tasks tracker update notifications
You can subscribe to this list here.
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: SourceForge.net <no...@so...> - 2011-05-04 02:48:09
|
Tasks item #3272568, was opened at 2011-04-03 14:08 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272568&group_id=515118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Mark Miesfeld (miesfeld) Assigned to: Mark Miesfeld (miesfeld) Summary: Produce the start of a concrete design document Initial Comment: So far there has been discussion of designing the RexxTill application up front, before just jumping in and writing code. But, this, at times a little vague, abstract discussion has not produce any concrete artifact. This task would involve simply getting a design document started and commited to the docs part of the repository. It doesn't involve writting a finished design document. The document itself could be empty. But, in order to produce a concrete document, there are a number of first steps that this task involves. Simple steps, but someone needs to step up and actually do the steps. The document needs a file name. There needs to be a decision as to what format the document should be in, plain text, Microsoft word, Open Office? The docs repository should probably have some subdirectories to organize the docs as the project starts to grow. For instance, eventually there would be a User Manual for the actual RexxTill application. The design related docs should probably be in a separate subdirectory than the user reference. With svn, eveything can be changed, while everything committed is always retained. So, the orignal subdirectory name for design docs can always be changed. The original name for a design doc can be changed later, etc.. The idea for this task is to simply get something concrete to start the process moving. ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2011-05-03 19:48 Message: Committed revision 15. This gives us something to start with, we still need to actually write it. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2011-04-30 17:50 Message: Since no else has jumped in on this, assigning it to myself. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272568&group_id=515118 |
|
From: SourceForge.net <no...@so...> - 2011-05-01 00:50:16
|
Tasks item #3272568, was opened at 2011-04-03 14:08 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272568&group_id=515118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark Miesfeld (miesfeld) >Assigned to: Mark Miesfeld (miesfeld) Summary: Produce the start of a concrete design document Initial Comment: So far there has been discussion of designing the RexxTill application up front, before just jumping in and writing code. But, this, at times a little vague, abstract discussion has not produce any concrete artifact. This task would involve simply getting a design document started and commited to the docs part of the repository. It doesn't involve writting a finished design document. The document itself could be empty. But, in order to produce a concrete document, there are a number of first steps that this task involves. Simple steps, but someone needs to step up and actually do the steps. The document needs a file name. There needs to be a decision as to what format the document should be in, plain text, Microsoft word, Open Office? The docs repository should probably have some subdirectories to organize the docs as the project starts to grow. For instance, eventually there would be a User Manual for the actual RexxTill application. The design related docs should probably be in a separate subdirectory than the user reference. With svn, eveything can be changed, while everything committed is always retained. So, the orignal subdirectory name for design docs can always be changed. The original name for a design doc can be changed later, etc.. The idea for this task is to simply get something concrete to start the process moving. ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2011-04-30 17:50 Message: Since no else has jumped in on this, assigning it to myself. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272568&group_id=515118 |
|
From: SourceForge.net <no...@so...> - 2011-05-01 00:48:19
|
Tasks item #3272494, was opened at 2011-04-03 12:54 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272494&group_id=515118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Mark Miesfeld (miesfeld) Assigned to: Mark Miesfeld (miesfeld) Summary: Determine RexxTill start up file and add to repository Initial Comment: Any application has to have a start up file. We should determine what the name for this file should be, produce an empty (does nothing) file that starts and quits, and commit it to the repository. This file should be totally independent of any design decisions, other than the one decision of what the name of the file should be. The new empty file would have nothing in it for command line arguments, if any, no requires statement, etc.. However, since the empty file should contain the license / copy right information it is dependent on the: "3272468 Drive decision on project license / add license file" tasks tracker item for completion. No reason that the decision on the name of the file can not get started. ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2011-04-30 17:48 Message: Committed revision 14. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2011-04-09 12:57 Message: Assigning this to myself. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272494&group_id=515118 |
|
From: SourceForge.net <no...@so...> - 2011-04-09 19:57:16
|
Tasks item #3272494, was opened at 2011-04-03 12:54 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272494&group_id=515118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark Miesfeld (miesfeld) >Assigned to: Mark Miesfeld (miesfeld) Summary: Determine RexxTill start up file and add to repository Initial Comment: Any application has to have a start up file. We should determine what the name for this file should be, produce an empty (does nothing) file that starts and quits, and commit it to the repository. This file should be totally independent of any design decisions, other than the one decision of what the name of the file should be. The new empty file would have nothing in it for command line arguments, if any, no requires statement, etc.. However, since the empty file should contain the license / copy right information it is dependent on the: "3272468 Drive decision on project license / add license file" tasks tracker item for completion. No reason that the decision on the name of the file can not get started. ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2011-04-09 12:57 Message: Assigning this to myself. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272494&group_id=515118 |
|
From: SourceForge.net <no...@so...> - 2011-04-04 00:11:27
|
Tasks item #3272841, was opened at 2011-04-04 00:11 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272841&group_id=515118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Database Logical/Physical Design Initial Comment: Finalize the database logical design so the physical layouts and table designs can be finalized adaptible to all kinds of relational database. Note: Logical Design to be done by the systems architect (Jon) and physical design aided by DBA (Ven). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272841&group_id=515118 |
|
From: SourceForge.net <no...@so...> - 2011-04-03 21:56:47
|
Tasks item #3272468, was opened at 2011-04-03 12:30 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272468&group_id=515118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark Miesfeld (miesfeld) >Assigned to: Mark Miesfeld (miesfeld) Summary: Drive decision on project license / add license file Initial Comment: This task involves taking the initiative to get a firm decision on which license the project will use and getting the project updated for that license. Part of getting the project updated would be getting the license file commited to the reposiitory, as open source projects always (usually) include the license file in a distribution. Part of this could also involve producing a template for the header of text files in the source code files. Most (all) open source projects have a standardized part of each source code file that includes some reference to the license and a copy right statement. ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2011-04-03 14:56 Message: Assigning this to myself ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272468&group_id=515118 |
|
From: SourceForge.net <no...@so...> - 2011-04-03 21:56:09
|
Tasks item #3272538, was opened at 2011-04-03 13:43 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272538&group_id=515118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark Miesfeld (miesfeld) >Assigned to: Jon Wolfers (sahananda) Summary: Formulate guidelines (or rules) for project membership Initial Comment: Currently this project has no statements, formal or informal, on who is, or how to become, a member of the project. The project should have some type of understanding on how to become a member of the project, what different roles, if any, that members of the project may have, some idea of expected responsibilites of members of the project. This need not be a formal written document, it could be just an informal discussion on the mailing list for instance. Although, there is nothing wrong with having a formal statement. A somewhat formal statement may prevent misunderstandings somewhere down the road. A good example of a formal statement is in the charter for ooRexx which can be found at: http://www.oorexx.org/charter.html Although this project may not need such a formal statement, and such a formal statement may not even be right for this project, it does contain some ideas that are almost universal to open source projects. These universal ideas may make a good starting point for discussion: * Only committers are allowed unrestricted write access to the source code repository. * Open source projects are a meritocracy, the more someone contributes to a project, the more that contributor is allowed to do within the project. * Open source projects usually have several differing roles within the project, from roles with voting rights on down to, typically, a user of the project. * Typically members with roles that do not include voting rights are promoted to roles with voting rights, through a vote of the members with voting rights. ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2011-04-03 14:56 Message: Jon - As the originator of this project, both the SourceForge project itself, but also the whole idea of a RexxTill application, I think you are the appropriate person for this task. So, I'm assigning it to you. That doesn't mean I'm in any hurry about it, I'm in no hurry at all. Plus, you can always just unassign yourself. <grin> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=2124059&aid=3272538&group_id=515118 |