Well i think we can use both, issues on github will be synchronized to jira and i think also the other way round, plus there are a few bonus on the atlassian platform. For now we could use github's and see if they'll grant an open source bonus. If not, it just won't be a big deal ...
Il giorno mercoledì 6 giugno 2012 17:13:12 UTC+2, Donovan ha scritto: > > If its on github just use github issues. > > On Jun 6, 2012, at 1:47 AM, francesco cislaghi <[email protected]> wrote: > > Hi Everyone, > > i asked about forking scalr and put a community version on github, and > Sebastian said that it'd be "very welcome" :). > I wanted to check the interest about this within the group. If enough > people think they might join and contribute, i'm going to upload it to > github. > I was thinking that afterwards we might ask an open source Atlassian > license and use jira as project management tool to keep track of bugs and > so on ... > > Please feel free to share your toughts on this matter. > > Francesco > > -- > You received this message because you are subscribed to the Google Groups > "scalr-discuss" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/scalr-discuss/-/8-GE6hXuCMkJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/scalr-discuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/scalr-discuss/-/CL_LRXV5_RMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en.
