start work on GitWeb

[cccs-ip]

GitWeb is GitHub Plus:

No milestones - we have something better.
Fine control over collaborator authorization
Deployments (like Springloops)
SubIssues - better than milestones

wiki and readthedocs later - probably as one better thing.

This may resonate with our super_project discussion:

Any issue may have multiple super_issues (UX allows assigning of sub issues too).
An issue with sub_issues cannot be closed until all sub_issues are closed
An issue has collaborators - the set of assignees applicable through the super/sub relation
An issue may have multiple required_issues (UX allows assigning of required_by too).
An issue may be OPEN, BLOCKED, or CLOSED.
An issue with required_issues that are not CLOSED is BLOCKED.
...

We may also support things like due dates for issues, dependencies, gantt charting but that will all be done over the API as a future thing.

What does this achieve?

Instead of milestones, you create an issue, 'Deliver foo', the relevant issues are added as sub_issues. Any issue can be broken down into simpler parts and the parts can potentially be assigned to other collaborators.

Listing will be smart with respect to showing/not showing sub issues. This needs some thought still.

Open Source - includes instructions to install/deploy own server like gitlab - AWS AMIs available both for GitWeb and for deployment environment (which the GitWeb AMI would be based on).
Built on Django/Django_rest_framework probably with AngularJS.

[cccs-ip]

I stumbled across this: https://github.com/bittner/django-organice

I can't tell what's inside just yet, but the site mentions:

Organice is a nice way to run a collaboration platform, an intranet, and websites for your business. It's a compilation of the best Django packages, preconfigured for getting you started quickly. Being powered by the well-known Django Web framework it's a safe choice for your IT investment providing an easily extensible architecture.

Fundamental Features

• Enables everyone to contribute to your content---while retaining your full control.
• Supports all four common collaboration and support patterns in several ways:
• Active contribution (create content, contribute corrections)
• Passive contribution (report issues, assign tasks, provide feedback)
• Active consumption (search and browse for content)
• Passive consumption (subscribe to notifications)
• Continually involves, helps and optimally supports your collaborators by sending out reminders, editing and submission hints to avoid losing traction or interest.

... sounds like it accomplishes a few things we're looking to do...

Otherwise, I was looking at Owncloud

[pwhipp]

organice might be a useful source of alternate apps.

ownCloud is quite cool. It has file versioning. Shame it is PHP.

The key weaknesses of ownCloud are that it is PHP and that it has file based versioning. It is active and has quite a range of apps.

GitWeb will have change based versioning (Git) and is not currently targeted at the cloud concept. It could be purposed in that direction - creating a very similar overall presentation to ownCloud including the possibility of plugging in apps.

[cccs-ip]

What should we do with the gitweb.org domain name?

[pwhipp]

Up to you. Pointing it at a CCCS page with some relevant notes might be best for the short term.

[cccs-ip]

gitweb.org now points to CCCS. I will make a page for it. For the moment, please help me with issue #182