Hi folks,
I was talking with Rolf on IRC, and I mentioned that a while ago I'd
brainstormed a list of features that would have been useful to my
workplace in particular.
Here are the list of things that would be appealing for Gitorious in
my workplace. These are just some rough ideas.
== Large features ==
* Issue tracking
* Atlassian Jira integration
* HTTPS push support
* SVN integration support that matches what GitHub does. Many of our
developers are old-school so SVN integration would help them ease into
learning Git.
* A web service API that matches GitHub's own API, so that all the existing
client libraries can use Gitorious as a drop-in replacement.
* Ability to apply merge requests from the web interface.
* Ability to mark a commit as "built" or "not built", similar to Travis' or
Jenkins' integration with GitHub's pull requests.
== Smaller features ==
* Ability to host on "git.example.com" (might already be implemented in the
latest Gitorious version).
* Auto-populate merge request form.
- If it is a single commit, use the first line of the commit as the subject,
and the rest of the commit body as the body of the MR.
- If it is multiple commits, use the name of the topic branch as the subject
(and leave the body blank.)
== Quotas ==
* Ability to limit large file checkins. Several developers have accidentally
checked in large binary files (particularly those who are unfamiliar with
Git). This is a quick way for users to inadvertently DDoS the system by
eating up a lot of memory and disk space.
* Per-repository quota support. Some discussion regarding implementation ideas
are here: https://groups.google.com/d/topic/gitorious/udkG5brBnTc/discussion
. Doing this at the filesystem level (making upcalls to the appropriate LVM /
BTRFS management commands) is attractive, because then the quota would truly
be inescapable for users, without crashing the rest of Gitorious. Several
web applications (eg OwnCloud) have a rudimentary implementation of quotas,
but they are tenuous because they are not enforced at the filesystem level.
== User management ==
* "All user emails" to easily send announcements to all users on the system.
Many users ignore GitLab's "HTML banner" feature because they simply don't
look at the web interface, or their eyes skip over it. It would be useful to
be able to blast out an email to all users, particularly within an
enterprise/fully managed environment such as ours.
* Better synchronization with with LDAP in order to discover which users have
left the organization, and determine what to do with their abandoned projects.
I regret that I was not able to implement these features in Gitorious
myself, and I'm happy to see that a couple of them (eg HTTP push
support) have already been done by Marcin. As it turns out, I've taken
a new job and will leave my current job on October 31st. Since my work
on Gitorious was related to my present job, I'm going to be stepping
away from the project. I should note this is not a request from my new
employer, just a personal decision. My wife and I had our first child
earlier this year and it's a matter of making time :)
I'll be unsubscribing from the Gitorious email list and leaving the
IRC room in a couple weeks. The admins should please feel free to
remove me as a manager/moderator for Google group and Wordpress blog
as well. I wish you all the best with future development!
- Ken
--
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
---
You received this message because you are subscribed to the Google Groups
"Gitorious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
