Re: [Userops] Free softwar community hosting

[Aaron Wolf]

That's why I don't think tying issues specifically to the same system as
the code is ideal. It's ideal to have the log-ins be the same, but
issues are not just about code and involve discussion etc.

I agree the way ikiwiki works is nice for a lot of reasons. I otherwise
think that each of these tools really are distinct: code merging and
review, ticketing, wiki, discussion… there's no perfect system that
mixes all these tools, there's always trade-offs.

Gitorious had no ticketing or wiki until recently and was still useful
for code-hosting and code review.

On 03/07/2015 04:17 PM, Jessica Tallon wrote:
> You nailed the reason why. The issue tracker currently isn’t just data in the 
> git repository that we can take from place to place it’s sat in some database 
> on some server that could go down and be lost. Your idea sounds really 
> awesome and my suspicion is that none of the free software issue trackers do 
> this, or at least those with code viewing and all of that stuff. This 
> solution would have to have a nice UI for users though as your average person 
> using Mediagoblin shouldn’t have to learn git to simply report an issue.
> 
>> 8 mar 2015 kl. 01:05 skrev Christopher Baines <address@hidden>:
>>
>> On 07/03/15 23:40, Jessica Tallon wrote:
>>> <snip> Large projects like GNU Mediagoblin or Inboxen don’t want to switch 
>>> over to find it vanishes one day.
>>
>> Just a small aside. Why?
>>
>> I imagine that your saying this because you believe the transition  from
>> one service to another would take a large amount of effort?
>>
>> I think one model that does really well in this regard is that used by
>> Ikiwiki [1] and Git Annex [2]. Each project just revolves around one git
>> repository. That repository is used for the source code, issue tracker,
>> website, wiki and forum. This means that you get all the Git goodness,
>> e.g. offline posting to the forum. Also, as Ikiwki is basically a static
>> site generator, this is very easy to replicate (on another machine).
>>
>> Another point, Git is great, because it federates. You can clone from
>> one service, and just push to another. I guess what this translates
>> across to in terms of issue tracking, is how easy it is to take your
>> issues elsewhere (just like you can take your sourcecode elsewhere with
>> Git)... I am unsure how the current set of free software issue trackers
>> do in this regard?
>>
>> [1] http://ikiwiki.info/
>> [2] https://git-annex.branchable.com/
>>
>>
>> _______________________________________________
>> Userops mailing list
>> address@hidden
>> http://lists.mediagoblin.org/listinfo/userops
> 
> 
> 
> _______________________________________________
> Userops mailing list
> address@hidden
> http://lists.mediagoblin.org/listinfo/userops
>