For activemq-web, I wouldnt see much issue in deleting that, since it
was purely for the website (which has changed and moved on over
several years since) and it doesnt seem like the repo was really used
for much at all before attention switched to the activemq-website repo
instead, which is where
I agree 100% with the following:
Good to archive/read-only:
- activemq-activeio
- activemq-nms-ems
- activemq-nms-xms
- activemq-nms-zmq
- activemq-nms-msmq
Should stay open for now:
- activemq-protobuf
I still think these are worth deleting:
- activemq-stomp
-
Agreed. Good call on the archiving.
Justin
On Thu, Apr 18, 2024 at 3:58 PM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> I don't think it's a good idea to delete anything unless it's just an empty
> repo so we can preserve the history.
>
> I think the standard practice is to
Hi Justin-
What about moving several to archived/read-only vs delete? Or at least
archive/read-only for a period of time before deleting them altogether?
Good to archive/read-only:
- [x] activemq-stomp (looks like stomp website)
- [x] activemq-web (looks like deprecated repo activemq-website is
I don't think it's a good idea to delete anything unless it's just an empty
repo so we can preserve the history.
I think the standard practice is to instead ask infra to archive the repos
and they become read only. We did that with Apollo:
https://github.com/apache/activemq-apollo
On Thu, Apr
During the process of researching the proposed move to GitHub Issues I
reviewed all ActiveMQ Git repos [1]. I noticed a handful that haven't been
updated in a long time and appear to be defunct:
- activemq-stomp - https://github.com/apache/activemq-stomp
- activemq-activeio -
