sluggo-issue-tracker / sluggo-py4web Goto Github PK

For CSE 183 MVP, I'm not going to worry about the license of the project, but if this is made available to others besides internally to Slugbotics it would be a good idea to give it an open source license. This should be completed by an alpha release.

I think the GNU GPL and GNU AGPL make the most sense, possibly MPL if any of the code ever needs to run on mobile devices (but since it's server-sided, this doesn't seem likely). AGPL is more restrictive and some organizations avoid tools with this license, which would be a downside.

Obviously, this is premature to worry about - just putting the issue here for later.

We should settle on some set of standards for how we contribute to the git repository, how to use branches, how/when to merge, etc.

This should be done before we start making any major contributions.

We should develop a preliminary data model for use in the tracker's database, along with how we intend to make it accessible in Python. This will also clarify how we intend to make all features accessible (for example, how different tickets, members, tags, etc. relate to one another)

We should figure out how we aim to organize different projects, tags, users, etc. in a Sluggo instance, so that we maintain the simplicity of the proposal while still enabling flexibility with how people choose to use the tool.

One idea (currently, what the proposal does) is to have one dumping ground for tickets, along with tags to assign issues to different teams. This seems to me a good solution, but we might want to see if this would conflict with any goals on Slugbotics (or other similar organizations). We also need to establish what ramifications this might have on other aspects of usage (security, restrictions, subteam roles, etc.). Perhaps this could lay in a tag, but then tags would need to have different access levels.