Version 1 vs 2
Version 1 vs 2
Content Changes
Content Changes
# Member feedback on 19th May proposals
...
# Member feedback on 19th May proposals
##Darsh (Arm)
Might be worth adding a link to the project’s CI on the project’s “mini-site”
##Anton (Arm)
There was a plan for a project dashboard showing “run-time” information / statistics / KPI. If it is hidden somewhere then worth to bring it up to a project area.
The topics split below is a bit unclear to me and looks overlapped.
image.png
{F119869}
##Minos (Arm)
The original schema proposes a commonly agreed set of entries for each of the mini projects hosted on the website
It may be worth it to separate the entries based on context to the three following categories:
###Mini-Project information
Elements should be used of the rendering of the mini-project landing page, and the graphics/marketing icons refereeing to it.
###Project Tools/ Navigation
The other entries in the schema are simply links to the corresponding purpose specific applications ( gerrit, jenkins, phabricator etc).
###Community engagement
A collection of contact points, as icons at the footer of the document.
###The delta to the original proposal could then look like this:
Legend
Original item
Proposed new item
Removed item
Comment
Original Schema
Project Title
Project Description
Project Documentation
Project Code
Project Mailing List
Project Call to Actions
Project Code Review
Project Useful Links
Proposed Schema
# Mini project Information
Project Title
Project Description (Full)
Project Icons
Project Background
Project Summary (Brief)
------------------------------
# Links/Buttons/ Tiles
Project Documentation
Project Code
Project Mailing List
Project Call to Actions
Project Code Review
Project Useful Links
-------------------------------
# Contact/ Community
Mailing List
Security Incident report
General Inquiries
Other communication channels ( irc/slack/.. )
An example reference bootstrap template could then be structured as such
----------------------- quick navigation bar (like the one currently on the page) ----------
####################
Mini Project Information
....
####################
News/ announcements
....
####################
Project Tools/Navigation
####################
Contact US/Community
####################
# Member feedback on 19th May proposals
...##Darsh (Arm)
Might be worth adding a link to the project’s CI on the project’s “mini-site”
##Anton (Arm)
There was a plan for a project dashboard showing “run-time” information / statistics / KPI. If it is hidden somewhere then worth to bring it up to a project area.
The topics split below is a bit unclear to me and looks overlapped.
image.png
{F119869}
##Minos (Arm)
The original schema proposes a commonly agreed set of entries for each of the mini projects hosted on the website
It may be worth it to separate the entries based on context to the three following categories:
###Mini-Project information
Elements should be used of the rendering of the mini-project landing page, and the graphics/marketing icons refereeing to it.
###Project Tools/ Navigation
The other entries in the schema are simply links to the corresponding purpose specific applications ( gerrit, jenkins, phabricator etc).
###Community engagement
A collection of contact points, as icons at the footer of the document.
###The delta to the original proposal could then look like this:
Legend
Original item
Proposed new item
Removed item
Comment
Original Schema
Project Title
Project Description
Project Documentation
Project Code
Project Mailing List
Project Call to Actions
Project Code Review
Project Useful Links
Proposed Schema
# Mini project Information
Project Title
Project Description (Full)
Project Icons
Project Background
Project Summary (Brief)
------------------------------
# Links/Buttons/ Tiles
Project Documentation
Project Code
Project Mailing List
Project Call to Actions
Project Code Review
Project Useful Links
-------------------------------
# Contact/ Community
Mailing List
Security Incident report
General Inquiries
Other communication channels ( irc/slack/.. )
An example reference bootstrap template could then be structured as such
----------------------- quick navigation bar (like the one currently on the page) ----------
####################
####################
####################
Project Tools/Navigation
####################
Contact US/Community
####################