Feature Requests
From ShareSource Wiki
Contents |
How to use this page
Basically, put in your idea at the end of this page.
Ideas
- Don't force the preview of things like bug reports - just include a "preview" button
- Change a project's category
- Allow single quotes in the project description
- Have a preview button in the project's wiki (when editing the wiki)
- Let projects specify the language(s) a project is written in
- <Mopman> i do think there should be a "status" option you can set per project though, just to get an idea of what the developers feel the status of the project is
- <Xrogaan> A graphical tree for the file vault / file release system, For maximum one click
- Calandar of Project's activities (maybe highlight more active days, display when jobs get done, eg how many bugs etc)
- Skins ?
- Subprojects with unlimited depth
- Includes phases, milestones etc. (see http://trac.edgewall.org/wiki/TracRoadmap for a similar existing implementation)
- project dependencies?
- Statistics results: who worked on which project
- Timeline/Gantt diagrams
- View related projects, files, tasks
- views for day, week and month
- Bookmark projects
- Project groups for IRC, say someone has a project in sharesource or just a large well populated channel then we could make special user groups (mainly host masks) of their project or channel.
Say someone has a project called "pythonbot" and they have the channel called "pythonbot" say the developers in that project would have the hostmask "pythonbot/developer/username" say if they was staff in the channel they would have "pythonbot/staff/username" or if they was just a regular user or supporter of the pythonbot project they could have "pythonbot/user/username" - Classical static web storage for e.g. source/API documentation such as Doxygen
- Statistics! For example hit count for project page, source repository (Subversion and Mercurial) read/write activity, file downloads count, etc.
Mercurial/DSCM wishlist
While it's certainly positive that ShareSource has adopted Mercurial, a true distributed SCM, the current ShareSource functionality hinders distributed development at best. There are no other public services offering better functionality, so ShareSoruce can be the first to truly support the various distributed development models. (see for example: [1])
Here's what ShareSource should implement to please DSCM gurus:
Multiple repositories per project (and "clone" on web interface)
- in many DSCM workflows, every developer has their own repository
- often, clones are preferred to "classical" branches; they're easier to understand
- separate components often stored in separate repositories with DSCMs
Manual "pull from URL" on the web interface
- D for "Distributed": repositories may be hosted anywhere; developers may want to host theirs at their company or own server
- Forcing all developers to use ShareSource won't work with DSCMs (especially considering the current limited functionality)
Ability to configure periodic pulls
- Ditto above
- Mirrors are crucial; DSCM repository mirrors aren't second-class citizens
- When using a separate repository, there's no need to enter ShareSource user/password for every "push"
- my software uses a non-standard licence. Basically it is public domain with one restriction, "non-military use only". You can do any thing you want with the source without payment or restriction other than you may not use it for the military or military contractors. Because of this, I can't find a home for my many Java projects. see http://mindprod.com/contact/roedy.html#NONMIL I can't believe so many people put out their software without such restrictions.
Packages
- Have an option to not make use of mirrors when releasing packages
- Rename a package or version title, and perhaps also rename the uploaded files
- Unlock a version for editing
- Add/edit descriptions for packages and versions
Files
- Show number of times downloaded
- Show date and time the file was uploaded
- Add/edit descriptions for files
