Activity
From 2013-04-15 to 2013-05-14
2013-05-14
-
17:19 action #457 (Closed): Assemble press kit.
- Gather everything and put it in a zip file in github (or somewhere else)
-
17:17 action #456 (Closed): Write 'reviewers guide', the mail for the press
- We send the press a 'personalized' email. It contains some personal notes from whoever sends it (usually Jos/the CM)....
-
17:12 action #455 (Closed): Create list of people who can be interviewed
- Release team, board members etc.
Ask them, get times and dates which are convenient (in the week between GM and GA... -
17:10 action #453 (Closed): Create a Press Kit and send it to the press
- This is the thing which gets us awesome reviews and "blogs like this":http://www.linux-magazine.com/Online/Blogs/Off-...
-
17:06 action #452 (Closed): Get screenshots taken
- Bug the openSUSE Artwork team and get help from the openSUSE team: we need screenshots. See https://en.opensuse.org/S...
-
17:03 action #451 (Closed): Get quotes from important people
- We usually quote one 'important' SUSE person first, putting the release into perspective. The second quote is usually...
-
16:46 action #450 (Closed): Assemble the Product highlights
- This is about creating a short-list of the best, most awesome, coolest features in openSUSE 13.1. It is CRUCIAL in wr...
-
16:27 action #449 (Closed): Write the community announcement mail
- This is a friendlier version of the announcement than the press release (which goes to opensuse-announce@opensuse.org...
-
16:22 action #447 (Closed): Write community announcement for news.o.o
- Based on the announcement and the feature guide & esp highlights, write a draft announcement for news.opensuse.org. T...
-
16:15 action #444 (Closed): Add features from distrowatch
- Check the packages from http://distrowatch.com/table.php?distribution=suse and add what's new. Check other sources, s...
-
16:11 action #442 (Closed): Get technical review
- The technical people in the openSUSE team need to go over the feature guide, check if it is correct and tell you what...
-
16:10 action #441 (Closed): Get features page finished
- Time to get that feature page finished.
Remember, try to talk at least about the packages from http://distrowatch.co... -
16:05 action #440 (Closed): Gather info from major pieces of our release onto Major_features page
- RC1 is out, so we know what we will ship.
Get the KDE stuff from the KDE announcement, the GNOME stuff from the GN... -
16:03 action #439 (Closed): Move Major Features to feature guide page
- Move content from https://en.opensuse.org/openSUSE:Major_features to https://en.opensuse.org/Features_13.1. Make sure...
-
16:01 action #438 (Closed): Get developers to add their features to our features list
- Kick the community to add their features to https://en.opensuse.org/openSUSE:Major_features
Email the project and ... -
15:57 action #437 (Closed): Write the Feature Guide
- The Feature Guide forms the base of our release marketing. It is a large list of the most important features in openS...
-
15:45 action #436 (Closed): Let our PR Agencies have one last look at the announcement
- After this it should be really ready to get into the press kit... No more changes!
-
15:43 action #435 (Closed): Get feedback on the draft press announce
- Show the announce to people both engineering and in SUSE marketing for feedback. Incorporate changes.
-
15:42 action #434 (Closed): Create a draft press announcement
- Take the feature highlights and use them to compose a first draft press announcement.
Some tips:
* Remember the 3x3... -
15:41 action #433 (Closed): Write Press Announcement for openSUSE 13.1
- Take the feature highlights and use them to compose a press announcement. Look at earlier announcements for the how
-
15:38 action #432 (Closed): Make sure we have the right people prepared to send out the social media messages
- Wiki page with social media contact people:
https://en.opensuse.org/openSUSE:Social_media_contacts
Contact them, ... -
15:37 action #431 (Closed): Create social media messages
- Create social media messages based on our release announcement & top features. See the openSUSE wiki:
https://en.ope... -
15:36 action #430 (Closed): Social media marketing
- Create a social media plan and social media messages; and get them translated. Also, prepare our social media channel...
-
15:33 action #429 (Closed): Sneek Peaks
- Write sneek peaks about various subjects. Ideas:
* Advanced GNOME tips (incl video?)
* Advanced KDE tips (incl vide... -
15:30 action #428 (Closed): Release Parties
- Organize release parties!
* Write release party invitation article
* Update release party wiki pages
* Organize re... -
15:25 action #427 (Closed): commit text to www.o.o
- Update opensuse.org with the new text snippet.
-
15:24 action #426 (Closed): Write snippet for www.o.o
- Write a piece of text announcing 13.1 for www.o.o. This can be based on the first 2 paragraphs of the announcement, s...
-
15:22 action #425 (Closed): Update openSUSE websites
- Get updates to:
* www.opensuse.org
* 13.1 wiki page
* More? -
13:42 action #392 (New): NUE: Release party organization
-
13:42 action #392 (Resolved): NUE: Release party organization
-
12:31 action #421 (Closed): Release Marketing
- Main task for Release Marketing:
* Social media marketing
* Sneek Peaks
* Release Parties
* Updated openSUSE webs... -
12:27 action #420 (Closed): Release Announcement
- Main task for everything around the release announcement:
* Press announcement
* Community announcement mail
* Com... -
09:20 action #175: deployment push access to www.opensuse.org
- Sent Matthew Ehle a mail
2013-05-13
-
20:22 action #397: Write announcement of Milestone 1
- 12.1: https://news.opensuse.org/2011/06/01/first-step-towards-12-1-with-milestone-1/
12.2: https://news.opensuse.org... -
17:44 action #397 (Closed): Write announcement of Milestone 1
- write the announcement...
See for example:
https://news.opensuse.org/2012/11/08/opensuse-12-3-milestone-1-is-read... -
18:15 action #417 (Closed): Send some info about RC 2 for the announcement to jos
- * Where are we, what got in, what is coming soon?
* anything else developers need to know?
* what to test specifica... -
18:15 action #416 (Closed): Write announcement of RC 2
- Write an announcement of the second RC. See older RC2 announcements on news.o.o for how.
-
18:15 action #415 (Closed): Publish announcement of RC 2
-
18:14 action #414 (Resolved): Write an article about adding the last packages and updates in time for openSUSE 13.1 Beta 1
- Style and text can be taken from
* https://news.opensuse.org/2011/09/27/get-your-package-in-factory-for-12-1/
* htt... -
18:05 action #413 (Closed): Write an article about testing openSUSE 13.1 release candidates
- Write an article about how people can help with testing.
Using openQA perhaps? Other tools? Testopia - there is st... -
17:57 action #412 (Closed): Send some info about RC 1 for the announcement to jos
- * Where are we, what got in, what is coming soon?
* anything else developers need to know?
* what to test specifica... -
17:57 action #411 (Closed): Write announcement of RC 1
- Write an announcement of the first beta. See older beta announcements on news.o.o for how.
-
17:57 action #410 (Closed): Publish announcement of RC 1
-
17:53 action #409 (Closed): Send some info about Beta 1 for the announcement to jos
- * Where are we, what got in, what is coming soon
* anything else developers need to know -
17:53 action #408 (Closed): Write announcement of Beta 1
- Write an announcement of the first beta. See older beta announcements on news.o.o for how.
Beta 1 needs to kick of... -
17:53 action #407 (Closed): Publish announcement of Beta 1
-
17:51 action #406 (Closed): Send some info about milestone 4 for the announcement to jos
- * Where are we, what got in, what is coming soon
* anything else developers need to know -
17:51 action #405 (Closed): Write announcement of Milestone 4
- Write an announcement of the milestone. See older milestone announcements on news.o.o for how.
Requirements:
* An... -
17:51 action #404 (Closed): Publish announcement of Milestone 4
-
17:49 action #403 (Closed): Write announcement of Milestone 3
- Write an announcement of the milestone. See older milestone announcements on news.o.o for how.
Requirements:
* An... -
17:49 action #402 (Closed): Send some info about milestone 3 for the announcement to jos
- * Where are we, what got in, what is coming soon
* anything else developers need to know -
17:49 action #401 (Closed): Publish announcement of Milestone 3
-
17:45 action #400 (Closed): Write announcement of Milestone 2
- Write an announcement of the milestone. See older milestone announcements on news.o.o for how.
Requirements:
* An... -
17:45 action #399 (Closed): Send some info about milestone 2 for the announcement to jos
- * Where are we, what got in, what is coming soon
* anything else developers need to know -
17:45 action #398 (Closed): Publish announcement of Milestone 2
-
17:33 action #394: Publish announcement of Milestone 1
- Sent an internal announcement about milestone 1
-
16:40 action #394 (Closed): Publish announcement of Milestone 1
- Write an announcement of the milestone. See older milestone announcements on news.o.o for how.
-
17:17 action #395 (Closed): Send some info about milestone 1 for the announcement to jos
- * Where are we, what got in, what is coming soon
* anything else developers need to know -
16:31 action #393 (Resolved): Add release party to the list of parties
- Launch party should be published on the list of community parties:
https://en.opensuse.org/openSUSE:Launch_parties -
16:31 action #392 (Resolved): NUE: Release party organization
- We will do a Release party the Release date in Nuremberg. In order for people of the company and community members to...
2013-04-20
-
15:22 action #358 (Closed): Redesign download.opensuse.org
- The download page of openSUSE distribution must be redesigned. The new design must make sure that the Release Notes a...
-
15:19 action #357 (Closed): Release notes during installation
- Present the release notes earlier during the installation process.
Should it be mandatory to go through them?
2013-04-18
-
11:17 action #343 (Closed): redesign download page
- The download page needs a redesign. Finding a way to make the references to the documentation esp the release notes m...
-
10:31 action #267 (Closed): create 13.1 release schedule
- Done.
16.5. M1
13.6. M2
11.7. M3
8.8. M4
19.9. Beta1
10.10. RC1
31.10. RC2
08.11. GM
Also available in: Atom