Re: [Aqsis-development] staging website changes
Brought to you by:
ltatkinson,
pgregory
From: Josh S. <str...@gm...> - 2012-03-26 14:46:45
|
I won't bother testing github's functionality as it seems pretty well documented. https://github.com/blog/957-introducing-issue-mentions I had Paul push a test commit to the aqsis repo with a jira ticket name in the commit message, and the commit shows up in the jira ticket under the "Commits" tab (see attached image). On Mon, Mar 26, 2012 at 6:10 AM, Josh Stratton <str...@gm...> wrote: > Github's issue tracker does seem much cleaner than other solutions. I > setup the test instance of jira for linking back to github and I'll > test the workflow for github and jira tracking and report back on the > pros and cons of each. > > On Mon, Mar 26, 2012 at 5:42 AM, François Beaune <di...@gm...> wrote: >> Jumping in, >> >> We were using Redmine for issue tracking in appleseed, it was working well >> but (1) it didn't track Github commits and (2) it proved to be too >> maintenance-heavy (we were on a dedicated server). We switched to Github's >> issue tracker and we're very happy about it. It does track commits (both >> ways, issues can reference commits and commits can reference issues), it has >> excellent labelling / tagging / filtering support and in general is much >> simpler and agreable to use than Bugzilla or Redmine. I can only recommend >> it. >> >> Cheers, >> Franz >> >> >> On Mon, Mar 26, 2012 at 5:37 AM, Josh Stratton <str...@gm...> >> wrote: >>> >>> Hey Everyone, >>> >>> I missed the meeting today, but read the discussion and wanted to >>> followup. I'm still pretty for the combined use of jira and >>> confluence and wanted to post my thoughts to some of the questions >>> raised in the meeting and the mailing list. >>> >>> -- Is jira a good issue tracker? -- >>> >>> Jira seems to have really good reviews by everyone I've heard from. >>> >>> -- Second, if we move to github (for example), they have an issue >>> tracker. Should we use that to stay integrated? Not spread too thin? >>> >>> Github has an issue tracker and it can be disabled just by checking a >>> box in the admin section of the repo. From what I saw on a repo of >>> mine, it totally removes all references of it so no one is going to >>> see "Issues are disabled" or something. >>> >>> I personally don't see too much integration github's issue tracker >>> actually provides. For what it is, it's fine. It seems to have basic >>> labeling across issues, but that's about it. I think jira pointing to >>> a github repo could actually integrate better as jira issues can >>> actually track commits against them. I don't think github can do >>> this. Maybe someone else can pipe-in here, but I don't know of any >>> integration github's tracker can do jira couldn't. >>> >>> As for being on different sites, I don't think this is too much of an >>> issue. I used the term "spreading too thin" about a year ago talking >>> about documentation when Leon mentioned it would be nice to have >>> several different documentation formats and I don't like the idea of >>> keeping something like that in sync. Having things on different >>> websites when the maintenance is relatively low isn't too much of an >>> issue. No one wanders into github project and starts looking at >>> issues to contribute. They go to the webpage and I think a lot of OSS >>> projects have external issue trackers like launchpad. I can still do >>> some styling to the wiki/jira side, but I think we might be missing >>> the point as our current wiki isn't really styled either besides an >>> aqsis logo (http://wiki.aqsis.org/). It would nice to have everything >>> on one site, but I think that's just way out of the scope a small >>> team. I'd rather see something on a website like: >>> >>> * go to this wiki for documentation (link to confluence) >>> * get the source code and browse trunk here (like to github) >>> * file issues here (link to jira) >>> >>> Confluence and Jira would have the same webpage, but that's a >>> coincidence, I guess. The alternatives (with respect to styles) is >>> having a separate tracker and wiki site, which kind of doesn't help. >>> I think it's okay to have separate sites to a certain extent. In the >>> example above, we'd use the basic functionality of github as a git >>> repo, provide statistics, etc. but I'd like to hear some motivations >>> of keeping everything "integrated" besides sharing a URL. I think >>> it's reasonable for new comers interested in aqsis development to know >>> where code lives, where documentation lives, and where issues are >>> tracked. >>> >>> -- Third, why confluence? -- >>> >>> I personally think confluence is a good editor for many tasks. It's >>> not perfect, but it works well. The biggest feature I like about >>> confluence is it's ability to integrate with jira. This would make >>> maintenance much simpler in my opinion. As discussed, if the wiki >>> focuses on non-source-related topics like development, it would be >>> very useful for pages like "Getting Started with Aqsis Development" or >>> "Bite-size Tasks" for new developers to always be up to date as we >>> make new jiras. >>> >>> As mentioned above, it would also keep the wiki and issue tracker on >>> the same site, which is a little better than using jira and some other >>> wiki. >>> >>> -- Fourth, won't confluence make us more dependent on closed-source >>> software? -- >>> >>> I know this is an issue for several people and it's totally legitimate >>> (especially after reading the Cathedral and Bazaar). However, for the >>> value it can provide, I still think it's a good choice. It's a really >>> good wiki and is hosted directly by Atlassian so we'd have virtually >>> no maintenance on the server end, which is again very important for a >>> small team. >>> >>> I don't have too much to say about this, but I can point to the Apache >>> Software Foundation's use of it. ASF is one of the largest OSS >>> community's in the world and I'm sure they didn't take any >>> dependencies on Atlassian lightly. The provide some brief feedback on >>> why they use Atlassian. >>> >>> https://cwiki.apache.org/CWIKI/ >>> >>> Obviously whatever ASF decides has no bearing on what everyone here >>> wants and I won't take it personally if we use something else, but I >>> do see using an Atlassian-serviced wiki as a great way to reduce our >>> workload. It's already setup on their side and all we'd ever have to >>> worry about is the content. I'm assuming other wiki software isn't >>> too complicated to setup or maintain, but it's still maintenance time >>> which seems rather precious at the moment. >>> >>> https://aqsisrenderer.atlassian.net/wiki/display/AQSIS/Home >>> >>> I'll try to make it to the next dev meeting to field some more of >>> these questions. >>> >>> Thanks, Josh >>> >>> On Wed, Mar 21, 2012 at 1:12 AM, Paul Gregory <pgr...@aq...> wrote: >>> > Personally, I'm not keen on moving everything over to Confluence, for a >>> > couple of reasons. >>> > >>> > 1. It looks far too "Atlassian". With WordPress we have complete freedom >>> > to >>> > style it to suit our needs. >>> > 2. It puts us in a weak position with regards to dependencies. Atlassian >>> > are >>> > a commercial organisation, they may change their policies regarding >>> > support >>> > for open source projects at any time, and we'd be in trouble. With >>> > WordPress, if anything should happen to our hosting options, we just >>> > package >>> > up, shift hosts, and unpackage. >>> > >>> > Unfortunately, I don't really have any good ideas how to alleviate this. >>> > My >>> > personal feelings would be not to use Confluence at all, for the reasons >>> > above, but instead have a wiki based on MediaWiki or similar. Something >>> > like >>> > this (http://ciarang.com/wiki/page/WPMW) might be interesting. This way >>> > we >>> > could maintain the appearance of a unified site, as we can style both >>> > WordPress and MediaWiki to our hearts content. I do however, advocate >>> > using >>> > Jira for bug tracking, it's a nice system. >>> > >>> > Excellent research though, glad to see some new ideas being bounced >>> > around. >>> > >>> > >>> > Paul >>> > >>> > On 20 March 2012 19:50, Josh Stratton <str...@gm...> wrote: >>> >> >>> >> Another possibility to unify the site is to put the parts under >>> >> wordpress on confluence since confluence is just as good as a CMS as >>> >> we won't be blogging much. The advantage of this is it would unify >>> >> the site completely--forums, jira, gallery, blog, etc. The downside >>> >> is it's slightly harder to style the wiki. Also being a wiki itself, >>> >> it looks a little less professional than a site with "last edited" and >>> >> such all over. >>> >> >>> >> https://aqsisrenderer.atlassian.net/wiki/display/AQSIS/Welcome+to+Aqsis >>> >> https://aqsisrenderer.atlassian.net/wiki/display/AQSIS/Gallery >>> >> >>> >> I personally don't like the idea of embedding the wiki pages. I'd >>> >> rather see the wiki as a separate site or move everything over to the >>> >> wiki. It's slightly less attractive, but as Chris mentioned, it might >>> >> actually look more professional having everything unified under one >>> >> site. Everyone, take a look at the above pages and let me know how it >>> >> looks. Some CSS stuff can be done on the wiki to make it more >>> >> readable. >>> >> >>> >> Thanks, Josh >>> >> >>> >> On Tue, Mar 20, 2012 at 10:00 AM, Josh Stratton >>> >> <str...@gm...> wrote: >>> >> > I added a background color to the unselected menu tabs and made the >>> >> > font bigger so they're easier to read. >>> >> > >>> >> > http://aqsis1.osuosl.org >>> >> > >>> >> > Also, as an experiment I made a couple of test pages with iframes >>> >> > that >>> >> > link to the documentation and jira. Not sure what I think if this. >>> >> > Might be frustrating for some people not having an updated url. I'm >>> >> > not sure if there's a better way to integrate this into wordpress or >>> >> > if we should just keep an external link. >>> >> > >>> >> > http://aqsis1.osuosl.org/index.php/support/embedded-issues/ >>> >> > http://aqsis1.osuosl.org/index.php/support/embedded-documentation/ >>> >> >>> >> >>> >> >>> >> ------------------------------------------------------------------------------ >>> >> This SF email is sponsosred by: >>> >> Try Windows Azure free for 90 days Click Here >>> >> http://p.sf.net/sfu/sfd2d-msazure >>> >> _______________________________________________ >>> >> Aqsis-development mailing list >>> >> Aqs...@li... >>> >> https://lists.sourceforge.net/lists/listinfo/aqsis-development >>> > >>> > >>> > >>> > >>> > ------------------------------------------------------------------------------ >>> > This SF email is sponsosred by: >>> > Try Windows Azure free for 90 days Click Here >>> > http://p.sf.net/sfu/sfd2d-msazure >>> > _______________________________________________ >>> > Aqsis-development mailing list >>> > Aqs...@li... >>> > https://lists.sourceforge.net/lists/listinfo/aqsis-development >>> > >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF email is sponsosred by: >>> Try Windows Azure free for 90 days Click Here >>> http://p.sf.net/sfu/sfd2d-msazure >>> _______________________________________________ >>> Aqsis-development mailing list >>> Aqs...@li... >>> https://lists.sourceforge.net/lists/listinfo/aqsis-development >> >> >> >> ------------------------------------------------------------------------------ >> This SF email is sponsosred by: >> Try Windows Azure free for 90 days Click Here >> http://p.sf.net/sfu/sfd2d-msazure >> _______________________________________________ >> Aqsis-development mailing list >> Aqs...@li... >> https://lists.sourceforge.net/lists/listinfo/aqsis-development >> |