5:04 a.m.
I +1 on the extra repo to remove the crap we all know we'll never want to look at
again.
wildfly-monitor is one such thing that I just want to delete - but if I can't just
outright delete it, then move it out of hawkular repo because its useless and will never
be used again.
----- Original Message -----
On Monday, May 02, 2016 10:14:17 AM Stefan Negrea wrote:
> Thank you,
> Stefan Negrea
>
> Software Engineer
>
> On Mon, May 2, 2016 at 2:50 AM, Thomas Heute <theute(a)redhat.com> wrote:
> > +1
>
> So far the count in this thread is 4 in favour and 2 against.
>
Count me in against this proposal. OBSOLETE is very well visible both in the
list of projects of the Hawkular org as well as at the project page itself. I
see no reason for creating more confusion with moving projects around. Just
let them live at the bottom of the project list, clearly marked as obsolete.
What if we realize we need to "unarchive" some project? I don't see that
happening but that would create even more confusion.
I'd say KISS.
>
>
>
> I changed last week the description of 2 repositories to show OBSOLETE in
>
> > the list view for that reason (-nest and -bus)
>
> 'Obsolete' or even 'retired' might be too strong, hence
'archived'. I see
> archived meaning that a repository no longer has active maintainers and it
> will not be used by active Hawkular projects. Also, we should not exclude
> the possibility of reviving some of the archived projects if needed again.
> Obsolete is very strong and has some implications on the tech or code,
> which might not be true for some repositories that no longer receive
> contributions.
>
> > On Fri, Apr 29, 2016 at 8:17 PM, Jay Shaughnessy <jshaughn(a)redhat.com>
> >
> > wrote:
> >> This seems like a good thing, a place for stuff to live, as an example
> >> or
> >> reference, or possibly to be revived later. Pinger and avail_creator
> >> may
> >> be good candidates as well.
> >>
> >>
> >> On 4/29/2016 12:42 PM, John Mazzitelli wrote:
> >>
> >> I would like to propose a new organization in Github to host projects
> >> that no longer receive development. "Hawkular-Archive" seems a
good name
> >> for this purpose. The goal is to keep the main Hawkular org focused on
> >> important projects and at the same time preserve work that was already
> >> done but away from the main organization.
> >>
> >> >From a quick look at the current organization here are two
repositories
> >> >that>>
> >> can be moved right away: hawkular-metrics-openshift (Openshit 2.x
> >> cartridge
> >> for Hawkular Metrics 0.2.7 or earlier) and hawkular-bus (code moved to
> >> another repo). Am I am sure we can find other repositories to move.
> >>
> >> In the long run we can develop some criteria for archiving projects but
> >> for
> >> now we can just do a one-time major cleanup.
> >>
> >> Any repositories that should be archived right away? Any other
> >> suggestions
> >> for a name? Any thoughts on the idea in general?
> >>
> >> This should be archived - it is obsolete - this was what the
> >> hawkular-agent grew out of, but this wildfly-monitor is no longer
> >> needed. https://github.com/hawkular/wildfly-monitor
> >> _______________________________________________
> >> hawkular-dev mailing
> >> listhawkular-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo
> >> /hawkular-dev
> >>
> >>
> >>
> >> _______________________________________________
> >> hawkular-dev mailing list
> >> hawkular-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
--
Lukas Krejci
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev