Mailing-List: contact dev-help@corinthia.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@corinthia.incubator.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 dennis.hamilton@acm.org does not designate 216.234.124.50 as permitted
 sender)
Reply-To: <dennis.hamilton@acm.org>
From: "Dennis E. Hamilton" <dennis.hamilton@acm.org>
To: <dev@corinthia.incubator.apache.org>
References: 
 <CAK2iWdQpQEwwPk2dO9hMmDhmZA1TDfDVx4va4Y4BmL23TnVtRA@mail.gmail.com>
In-Reply-To: 
 <CAK2iWdQpQEwwPk2dO9hMmDhmZA1TDfDVx4va4Y4BmL23TnVtRA@mail.gmail.com>
Subject: RE: A little new information about wiki, jira, web etc.
Date: Fri, 19 Dec 2014 11:35:10 -0800
Organization: NuovoDoc
Message-ID: <006a01d01bc2$e806a7a0$b813f6e0$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQDjBMpVdrOxAkHlKBbRUSsVnYUPL55xbIoA
Content-Language: en-us
Received-SPF: softfail (supercp.com: domain of transitioning
 dennis.hamilton@acm.org does not designate 97.113.57.118 as permitted sender)

My current account works on the JIRA.  I assume that I can create issues =
and comment on them, but perhaps not do much else?

 +1 on tying commits to issues.

With regard to the migration, I suggest that only open  issues by =
someone now on the project be brought over.

I suppose there needs to be some announcement about moving there on =
uxproductivity/Corinthia.  It depends on what Peter wants to do with =
that one now that the Apache code base and mirror are operating. =20

If it were mine, I would delete it, although that would disconnect any =
forks and clones.  Perhaps a notice in the README.md there is =
sufficient, letting it sit for a while.  It might not matter until Peter =
is up against the 5-repository free limit.

-----Original Message-----
From: jan i [mailto:jani@apache.org]=20
Sent: Friday, December 19, 2014 07:49
To: dev@corinthia.incubator.apache.org
Subject: A little new information about wiki, jira, web etc.

[ ... ]

Our jia (issues) is now online, I am currently the administrator, but =
are
happy to hand it over to someone else. You will need to make a jira user =
if
you dont already have one. As admin I can then allow you to =
create/update
etc issues. We need a discussion on how we want to use jira, solely for
issues or also for wishes etc. we can even connect our commits with an
issue. I will next week upload our current issues (not all, I will be
selective)

[ ... ]