Plus we've redone the website and regularly run a link checker -- OP let us
know if you've any lingering reservations (apart from the clunky mailing
lists which I'm fond of -- kinda makes me wish we had a gopher site!)

On 27 January 2017 at 16:35, Andrea Turli (JIRA) <[email protected]> wrote:

>
>      [ https://issues.apache.org/jira/browse/BROOKLYN-111?page=
> com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Andrea Turli closed BROOKLYN-111.
> ---------------------------------
>     Resolution: Not A Bug
>
> > Can't find any useful help / fork Brooklyn thanks to Apache Incubation &
> dependence on archaic mailing lists
> > ------------------------------------------------------------
> ------------------------------------------------
> >
> >                 Key: BROOKLYN-111
> >                 URL: https://issues.apache.org/jira/browse/BROOKLYN-111
> >             Project: Brooklyn
> >          Issue Type: Bug
> >    Affects Versions: 0.7.0-M1, 0.7.0-M2, 0.7.0
> >         Environment: World
> >            Reporter: Hok Shun Poon
> >            Priority: Critical
> >
> > The only way I can get any help around the fantastic project that is
> Brooklyn is through mIRC. What is going on?
> > There's no record of any solutions that people have worked out anywhere.
> > There's little record of who is responsible for the project, and lesser
> still, their contact details. You have to extract these details from GitHub
> commits.
> > Brooklyn Google Groups were killed off in a massive step back into the
> dark ages to the [email protected] mailing list thanks to
> Apache's insistence of moving all project infrastructure to Apache.
> > I file an issue on GitHub and I'm told I need to file it AGAIN in JIRA,
> where the project is actually tracked.
> > The website has broken links absolutely everywhere, 6 months after the
> Incubation started.
> > What is this all about?
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Reply via email to