On Sat, Feb 21, 2015 at 7:21 PM, Olemis Lang <ole...@gmail.com> wrote:
> Just an initial comments : at least in (all) my browser(s) trac-hacks > image/icon overflows available space . > I haven't been able to determine the cause of that issue. It is captured in: http://trac-hacks.org/ticket/12169 > On 2/21/15, RjOllos <rjol...@gmail.com> wrote: > > On Thursday, February 19, 2015 at 5:54:55 PM UTC-8, RjOllos wrote: > >> > [...] > >> > >> We have a trac-hacks organization on GitHub (2). > [...] > >> > >> I've started by inviting a bunch of users to join the trac-hacks > >> organization. I found those users through a search for "trac plugin" and > >> filtering the false positives. I've received a half-dozen positive > >> responses in the first few hours, so you'll see more repositories > >> appearing > >> on the organization page. > >> > >> If you have a GitHub repository that you'd like to associate with the > >> organization, please contact me or just reply here. > > In the last few years I've developed quite a few Trac plugins , > extensions even whole projects from scratch . Some of them have been > developed for a third-party . Therefore licensing is different (e.g. > GPL) and owners might want to retain their (ownership / central point > of distribution / copyright) over the plugin rather than yielding > control to the Trac-Hacks organization and being owners indirectly . > Summarizing the existing, somewhat informal policies: anyone publishing a plugin to trac-hacks retains full control over the plugin, until such time as they voluntarily give up the plugin or can no longer be reached. Plugin authors are free to choose the license for their plugin. So far we don't even prevent publishing of software on trac-hacks for which the source code is not provided. Several times Steffen (hasienda) and I have discussed the need for more formal policies that are developed by the community. So far neither of us has found the time to push this effort though. > Nevertheless there might be an interest for being indexed in there . > Is there anything that can be done in this case ? > Anyone is free to create a wiki page on trac-hacks.org that contains links to an external issue tracker, repository, etc ... The only thing I would ask of potential hack creators, and this is not a formal rule that has been written by the community but rather something that just seems sensible to me, is that you don't create the hack until the external project exists and is actually usable. Over the years there have been several hacks created for projects that are never developed. These just take up space and eventually one of us has to remove them. If you wish to create a page in order to develop a plugin in a trac-hacks repository, that is a different scenario and it makes sense to create the hack in order to have a place to work from. > OTOH could you please clarify (maybe a blog post is better) the items > below ? > > 1. how is the repository setup ? > - e.g. permissions / ownership but not limited to that > There is a "Admin access team" associated with each repository. The user who transfers the repository becomes the sole member of the "Admin access team" for the repository. No other users have write-access to the repository unless granted by the repository author. "Admin access team" permissions are described here: https://help.github.com/articles/permission-levels-for-an-organization-repository/#repository-access-teams 2. how to join the organization @ Github ? IOW > - Only repositories join the organization ? > - Will plugin authors join the organization as well ? How ? > Plugin authors join the organization along with their repositories. I proposed in the blog post that anyone with an interest in trac-hacks may join the organization. Unfortunately it appears that I must send an invite to every user; there is no way for a user to request an invite through the trac-hacks organization page on GitHub. I sent an inquiry to GitHub about this yesterday but so far haven't received a reply. So if you'd like an invite, just let me know. With the features provided by GitHub this is the best way I could see to setup the organization. It's a work-in-progress, so feedback is good in helping to improve the process. If anyone hits a roadblock in trying to do something, please post to the list. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
