Please see this post for the latest discussion.
So, as mentioned in the latest status update the release team is rising, phoenix like, from the ashes of the last attempt.
This is the nomination thread, you may either nominate yourself or someone else, but that person must then confirm that they can make the time commitment needed to be part of the team and that they actually want to!
What is the release team?
The release team is what takes apps from development test to pre-release and then on to official release. The release teams tests and provides feedback on programs in the Beta Testing forum.
What do I need to commit to?
This is subject to change but the current thought is one app per week, for either 3 or 6 months. You will need to test the app for portability, and provide feedback on its compatibility with the Format. This is not a huge amount of time, but the comitment is important, this team needs to be stable and start churning out apps for it to be a success.
What to I need to do?
If you are nominating someone else then just drop their name below along with why you think they would be great for the role. If you are nominating yourself then similar rules apply, just say why you would like to take part, what skills you have and anything else that you think is relevant. Since the universal launcher is written in NSIS knowledge of it is obviously a plus, but if you are willing to learn that would be fine to, a mix of experience is normally a benefit to a team. Having used tools such as Regshot would also be good but I expect documentation will be provided to help if you haven't. All uses who are nominated must have been developers or active on the forums for the past six months.
Good luck all!
[Topic locked by SL, lets discuss this more first, I can reopen it later]
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
I think that before we jump into the Release Team again, we need to stop, consider what we're doing, formulate a detailed plan, consider all that needs doing in considerable detail so that we can make informed commitments. I think it would work well for us to form a working group to work all this out. And so I think I would prefer nominations to be of members to nut it all out in this working group. A page to work it out on would be good, the ability to chat with one another, possibly even a voice or video conference call at points could be useful in working out what we're doing. If we make a requirements plan, a schedule, work out exactly what we're doing and get people to agree with that of their own volition (rather than saying a month later "hey! I didn't sign up for that!") I think we've got far more chance of succeeding.
I'd put a rough schedule on that process putting us back a month or so if it were done well and thoroughly, possibly more depending on other commitments and developments at PortableApps.com.
(I've just been reading Rapid Development and Code Complete by Steve McConnell; they're great books, you should all read them. I think if we all read them and applied them to here we'd get a lot more done more quickly. I wish I'd read them a year or two ago.)
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
what it is worth I agree 100% with this.
Would you guys like to start now, then? We could start the conversation in the forums now and let everyone -- whether interested in joining, developers or just members with good ideas -- contribute to what will become the initial guidelines.
Sometimes, the impossible can become possible, if you're awesome!
It would also be useful to look back at the history of release here and get some stats. We should do this for apps that are heavily supported and pushed here (like Firefox) as well as those that tend to fall by the wayside, to get a realistic view.
We should be asking questions like this:
How long does it take now to get an app from dev test to full release? What necessary steps take the longest? What are the roadblocks?
How many apps do we have in the dev test stage? (By my count, on the test release page, there are 4 pre-release and 165 dev test apps, and I'm sure that there are others that haven't made it to that page.) How do we prioritize that many apps?
To what extent the release team will be doing beta testing of apps?
BTW, I'm not suggesting that these questions get answered in this thread. These are just ideas of things that need to be asked during the planning sessions.
I made this half-pony, half-monkey monster to please you.