<div dir="ltr">If that's true, then why do all the WG have separate repos for issues to make them public? If WG issues are only for internal discussion, then why can't they just be issues on the WG's fork of the spec? It seems that the public visibility of <a href="https://github.com/mpi-forum/mpi-issues">https://github.com/mpi-forum/mpi-issues</a> alone accomplishes what we had before we Trac.<div><br></div><div>Jeff</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 9, 2015 at 6:33 AM, Bland, Wesley <span dir="ltr"><<a href="mailto:wesley.bland@intel.com" target="_blank">wesley.bland@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Trac Tickets == mpi-forum/mpi-issues<br>
<br>
If you have an issue that was already in the old Trac system, then it probably belongs in mpi-forum/mpi-issues. Working group issues are just internal things for the working groups to discuss.<br>
<br>
From: mpi-forum on behalf of Jeff Hammond<br>
Reply-To: MPI Forum<br>
Date: Monday, November 9, 2015 at 7:40 AM<br>
To: MPI Forum<br>
<span class="">Subject: Re: [Mpi-forum] Github GitHub GITHUB!<br>
<br>
</span><span class="">Where do issues migrate if they have no associated working group? For example, <a href="https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/318" rel="noreferrer" target="_blank">https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/318</a> is important to me, but we do not have a datatypes working group, just a chapter committee.<br>
<br>
Because of the similarity between large-count and extended precision plus my interest in both, I am inlined to migrate that issue into <a href="https://github.com/mpiwg-large-count/large-count-issues" rel="noreferrer" target="_blank">https://github.com/mpiwg-large-count/large-count-issues</a>, but this may not work for all of them.<br>
<br>
Because of the ambiguity in the migration process for some issues, I propose that we defer making Trac readonly until the end of the year.<br>
<br>
Jeff<br>
<br>
</span><span class="">On Thu, Oct 22, 2015 at 11:24 AM, Jeff Squyres (jsquyres) <<a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a><mailto:<a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a>>> wrote:<br>
If you didn't read Wesley's detailed email (YOU SHOULD! ...but I know not everyone will :-( ), here's the executive summary:<br>
<br>
1. Read Wesley's email: <a href="http://lists.mpi-forum.org/mpi-forum/2015/10/3112.php" rel="noreferrer" target="_blank">http://lists.mpi-forum.org/mpi-forum/2015/10/3112.php</a><br>
<br>
2. Send Wesley/Jeff your Github ID.<br>
<br>
3. Start moving any still-open Trac tickets to Github.<br>
<br>
4. SVN is already read-only. Everything has been moved to Git repos on GitHub.<br>
<br>
5. Trac goes read-only on Fri, 13 Nov 2015<br>
<br>
6. Lots of good information is on our wiki: <a href="https://github.com/mpi-forum/mpi-issues/wiki" rel="noreferrer" target="_blank">https://github.com/mpi-forum/mpi-issues/wiki</a><br>
- There's info for Git newbies<br>
- There's info for GitHub newbies<br>
- There's info about how the Forum uses GitHub<br>
<br>
7. The Dec 2015 MPI Forum meeting will only accept Github Issue agenda items (not Trac tickets).<br>
<br>
8. Read Wesley's email: <a href="http://lists.mpi-forum.org/mpi-forum/2015/10/3112.php" rel="noreferrer" target="_blank">http://lists.mpi-forum.org/mpi-forum/2015/10/3112.php</a><br>
<br>
--<br>
Jeff Squyres<br>
</span><a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a><mailto:<a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a>><br>
<span class="">For corporate legal information go to: <a href="http://www.cisco.com/web/about/doing_business/legal/cri/" rel="noreferrer" target="_blank">http://www.cisco.com/web/about/doing_business/legal/cri/</a><br>
<br>
_______________________________________________<br>
mpi-forum mailing list<br>
</span><a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a><mailto:<a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a>><br>
<span class=""><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum" rel="noreferrer" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum</a><br>
<br>
<br>
<br>
--<br>
Jeff Hammond<br>
</span><a href="mailto:jeff.science@gmail.com">jeff.science@gmail.com</a><mailto:<a href="mailto:jeff.science@gmail.com">jeff.science@gmail.com</a>><br>
<a href="http://jeffhammond.github.io/" rel="noreferrer" target="_blank">http://jeffhammond.github.io/</a><br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
mpi-forum mailing list<br>
<a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a><br>
<a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum" rel="noreferrer" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Jeff Hammond<br><a href="mailto:jeff.science@gmail.com" target="_blank">jeff.science@gmail.com</a><br><a href="http://jeffhammond.github.io/" target="_blank">http://jeffhammond.github.io/</a></div>
</div>