Artwork Team Roadmap for Trusty

Registered by amjjawad  on 2013-12-05

https://wiki.ubuntu.com/UbuntuGNOME/Artwork

https://launchpad.net/~ubuntugnome-artwork

Ubuntu GNOME Artwork Team needs to have a clear plan/vision (AKA Roadmap) for Trusty Tahr Cycle

This blueprint to discuss all the possible suggestions/ideas for a roadmap for this sub-team

- Set clear goals
- Set clear tasks
- Define the roles of each member
- Assign task for each member

And so on

==================================================
HOWTO Edit White Board
https://wiki.ubuntu.com/UbuntuGNOME/Brainstorming#How_To_Edit_The_Whiteboard_on_Blueprints
==================================================

Blueprint information

Status:
Complete
Approver:
amjjawad 
Priority:
Essential
Drafter:
amjjawad 
Direction:
Approved
Assignee:
Registry Administrators
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
amjjawad  on 2013-12-27
Completed by
amjjawad  on 2014-04-17

Related branches

Sprints

Whiteboard

[amjjawad - Roadmap Proposal]
1- TO-DO for this cycle (Trusty Tahr): https://blueprints.launchpad.net/ubuntugnome-brainstorming/+spec/artwork-trusty-tahr

2- PROPOSAL: https://blueprints.launchpad.net/ubuntugnome-brainstorming/+spec/wallpaper-contest - Highly Recommended

3- Recruit More Contributors - two at least to help Ubuntu GNOME Artwork Team Leader and to cover his absence if he is away for vacation or Real Life issue.

4- Discuss (in a meeting OR on the mailing list) all the above + other 'possible' suggestion as far as the time allows.
-----------------

These are my suggestions for the roadmap of Ubuntu GNOME Artwork Team :)

+1 = Agree
0 = don't know/not sure/don't want to vote
-1 = Disagree

Feel Free to Edit the Whiteboard with any comment in mind :)

Thank you!
----------------------------------------------------------------------------------------------------------------------------

[aldomann] I think we should create a Wiki page with our schedules and work items (ubiquity, logos, contest, etc.) so that anyone can check their completion status. Anything important we need to announce would be done in the mailing list. The same applies to feedback requests. What do you think?
----------------------------------------------------------------------------------------------------------------------------

[amjjawad] [RE: aldomann] but that is a double work IMHO. I have created a dedicated team (Brainstorming) and setup these blueprints for such thing. IMHO, everyone needs to be more familiar with blueprints. Creating 'more' Wiki Pages is, IMHO, waste of time + resources + energy. Launchpad offers you out-of-the-box tools to handle any project :D

Yes. Mailing list = announcement and important discussions.
Meetings are very important as well.

As for feedback, anyone who has a feedback he/she needs to send either to Artwork Mailing List and/or the general mailing list:
https://wiki.ubuntu.com/UbuntuGNOME/ContactUs#Contact_Us

----------------------------------------------------------------------------------------------------------------------------
[aldomann] That's true my friend. I'll make blueprints for our targets for this release ;)

(?)

Work Items

Work items:
1- https://blueprints.launchpad.net/ubuntugnome-brainstorming/+spec/artwork-trusty-tahr : DONE
2- https://blueprints.launchpad.net/ubuntugnome-brainstorming/+spec/wallpaper-contest : DONE
3- Recruit More Contributors - two at least to help Ubuntu GNOME Artwork Team Leader and to cover his absence if he is away for vacation or Real Life issue - https://lists.ubuntu.com/archives/ubuntu-gnome/2013-December/001286.html : DONE
4- Discuss (in a meeting OR on the mailing list) all the above + other 'possible' suggestion as far as the time allows : DONE
5- Improve the internal communications between the members of Artwork Team and with the whole family of Ubuntu GNOME to avoid possible mistakes, delays, etc : TODO
6- https://blueprints.launchpad.net/ubuntugnome-brainstorming/+spec/logo-roundel-redesign : TODO

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.