Quote from: rthrash at Feb 27, 2006, 01:57 PMThe reason that project description is there because I’ve just requested the modxcms project at Sourceforge.net.
Waow, that’s great news !
(Sorry I have been out a bit this past few days, I’ll definitely catch up on everything I intended to do by the end of the week...)
.: COO - Commerce Guys - Community Driven Innovation :.
MODx est l'outil id
-
MODX Staff
- 2,502 Posts
Reviving this thread for a status request.
Upon review of this thread and some of the sites, it looks like this has been let to whither. I am wondering if we are still interested in being involved in the listing sites. While there are merits to being on some of these there are limits to what can be managed by the team. That being said I think that we could develop a deployment schedule that triggers an update process for releases so that the locations such as sourceforge and the like always have a current.
Cheers,
Jay
Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup
magician.
Blog ✦
Twitter ✦
LinkedIn ✦
GitHub
-
MODX Staff
- 10,725 Posts
If someone will collect email addresses we can notify, I can have production build scripts email the list with details of the new release right after it publishes the new releases to the download site.
-
MODX Staff
- 12,272 Posts
I think most of the sites require manually updating a form. :/
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
MODX Staff
- 2,502 Posts
If we are interested in this I want to make this part of a Release Actions Checklist. I want to make it so no matter who comes and goes that whenever a release is issues there are certain things that ought to be done so there is a predictable cycle for every release and team members and community members are not going: "I wonder if we should do XY or Z"
Not a policy but a little procedure sheet for marketing when releases are coming. Marketing can handle disseminating packages and issuing statements for such sites and there are other people who we may want to inform as well and press releases and such.
I guess I would need to know what sites we should be sending to. Only those with traffic and have our "competitors"
Cheers,
Jay
Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup
magician.
Blog ✦
Twitter ✦
LinkedIn ✦
GitHub
Agreed, that’s great !
If we can manage to regain access to the account on cmsmatrix (we don’t know who submitted MODx there, and we don’t have the password), that would be great... if only they responded to email we send about it, it would be easier
.: COO - Commerce Guys - Community Driven Innovation :.
MODx est l'outil id