Final TitanPad for Plone Planning and Organizing Sprint 2016

the planning and outcomes document of the sprint

text/html hv7uZiFc2f-latest.html — 29 KB

File contents

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<meta http-equiv="Content-type" content="text/html; charset=utf-8" />
<title>hv7uZiFc2f</title>
</head>
<body>---------------------------------------------------------------------------<br
/>This is a shared scratch pad/note taking area created for the Plone planning &amp; organising sprint held at Amterdam, The Netherlands from july 30th to august 1st.&nbsp;<br
/><br
/>These are not finished guidelines, proposals or whatever definitive things, but live minutes to help with discussing various planning and organising issues, problems, ideas and tasks for the Plone Community.&nbsp;<br
/><br
/>Present at the sprint location in Amsterdam:<br
/><ul><li>Alexander Loechel</li
><li>Christine Baumgartner</li
><li>Fred van Dijk</li
><li>Paul Roeland</li
><li>Sven Strack</li
><li>Maurits van Rees<br/><br
/></li></ul
>Additional Remote Sprinters that was present at some time:<br
/><ul><li>Philip Bauer</li
><li>Kim Nugyen</li
><li>Stefania Trabucchi</li
><li>Dylan Jay<br/><br
/></li></ul
>---------------------------------------------------------------------------------------------------------<br
/>P&amp;O Sprint saturday july 31st. Make a more extensive list of non programming tasks<br
/>that we could do this weekend, also so that remote sprinters can pick smaller tasks. Loosely<br
/>followed from the topics written on the sprint page at coactivate.<br
/><br
/>Non developer/programming tasks that could be done&nbsp;<br
/><br
/>planning, what could we do today/saturday/tomorrow?&nbsp;<br
/><ul><li><s>analyse add'on story</s></li
><li>plone.org&nbsp;<ul><li>doormat cleanup on plone.org</li
><li>evaluate plone.org related sites listing</li
><li><s>downloads section is confusing.</s><ul><li><s>There are open tickets. In geeneral make it easier for people to find stuff.</s></li></ul
></li
><li><s>Security hotfix pages are confusing</s><ul><li><s>sorted alphabetically</s></li
><li><s>analyse further improvements</s></li></ul
></li
><li>documentation on badge-system, how to assign them etc.<ul><li>lifelong badges, alumni badges</li
><li>listing of the community people with their badges? Not there yet</li></ul
></li
><li>getting the stats working? What is needed to make it work?<ul><li>number of pull requests</li
><li>number of open issues?&nbsp;</li
><li>stackoverflow rewards</li
><li>design fun other metrics to show community activity?</li></ul
></li></ul
></li
><li>plone.com and plone.org miss a top bar redirecting to the other sites (docs, com, org. community)<ul><li>Executive session</li></ul
></li
><li>docs.plone.org<ul><li>does somebody has a clear idea on elasticsearch search for sphinx to improve search?<ul><li>writethedocs has hosted support from elastic itself, but no public info</li></ul
></li></ul
></li
><li>In general website presence<ul><li>Identify Pages on Plone.org and Plone.com and other Plone Portals that need some love</li
><li>make a list of providers/sites where you can get a hosted plone<ul><li>free &amp; paid hosters (heroku, flyingcircus</li></ul
></li></ul
></li
><li>plone.net -&gt; old.plone.org -&gt; plone.com<ul><li>steve mcmahon or Martior.</li></ul
></li
><li>plone.com<ul><li>Should/ do we want a geographical map for the provider listing?</li
><li>Should providers have tags for vertical markets or other classifications that fit into isotope?<ul><li>make the listing more useful for potential customers without forcing providers into too narrow classification</li></ul
></li
><li>links from provider detail page to success story detail page?&nbsp;</li></ul
></li
><li>training.plone.org<ul><li>front page?&nbsp; Need nice descriptions?&nbsp; &lt;- Philip</li
><li>content on docs.plone.org vs detailed training descriptions on training.plone.org. ...<br/><br
/><br/><br
/><br/><br
/></li></ul
></li></ul
>-------------------------------<br
/>P&amp;O sprint friday morning 30-07, listing of all teams<br
/><br
/><br
/><br
/><br
/><b>Plone teams (both 'formal' and informal):</b><br
/><br
/><br
/><ul><li>Plone Foundation Board of Directors</li
><li>Plone Foundation Membership Committee</li
><li>Framework Team</li
><li>Security Team</li
><li>AI-Team</li
><li>Documentation</li
><li>Training Team</li
><li>Communication</li
><li>Release Team (releases the software packages, see tasks)</li
><li>Build-Team</li
><li>Testing-Team</li
><li>Usabilty-Team</li
><li>Accessibilty-Team</li
><li>Plone.org Team</li
><li>Plone.com Team</li
><li>i18n-Team</li
><li>Ploneconf Team</li
><li>Launch Team (New Plone 5 release)<br/><br
/><br/><br
/></li
><li>Interest Groups<ul><li>PloneEDU</li
><li>PloneGov<br/><br
/><br/><br
/><br/><br
/></li></ul
></li
><li>Plone Suites<ul><li>PloneIntranet (Quaive)</li
><li>CastleCMS</li
><li>elevateIT</li
><li>VNC</li
><li>Bika LIMS lab info mgmt system&nbsp;<br/><br
/><br/><br
/><br/><br
/></li></ul
></li></ul
><b>Plone Domains in use</b><br
/><br
/><ul><li>plone.org castaway</li
><li>plone.com</li
><li>docs.plone.org</li
><li>training.plone.org</li
><li>jenkins.plone.org</li
><li>community.plone.org</li
><li>dist.plone.org</li
><li>ploneconf.org</li
><li>plonesymp.org</li
><li>planet.plone.org</li
><li>dev.plone.org</li
><li>archive.plone.org<br/><br
/><br/><br
/><br/><br
/><br/><br
/></li></ul
><b>Tasks that are unassigned or where the process is unclear</b><br
/><br
/>* response and coordination of bug reports (non-criticals, non-security relevant) for all Plone packages.<br
/>* managing incoming pull requests (non-PLIPables)<br
/><br
/><br
/><b>Documentation gaps:</b><br
/><ul><li>plone.org 'badges' process: how to give them out, who gives them out, do team badges get removed if people are no longer on a team or do they get 'alumni' status?<br/><br
/><br/><br
/><br/><br
/></li></ul
>List of persona's/ target groups so we are using the same (temporary) definitions during the discussions/brainstorming:<br
/><br
/>----------------------------------------------------------------------------------------<br
/>P&amp;O Sprint friday 30th july afternoon. listing of target groups/umfeld for which the plone community creates software/information/value.&nbsp;<br
/><br
/>We found out that we sometimes mean different things under the same name, for example what an integrator or a solutions provider is. So we created this list to avoid misunderstandings during the sprint.&nbsp;<br
/><br
/><br
/><b>Decision Maker</b><br
/>- I need an Information system to solve a problem.&nbsp; Can I use Plone for That?&nbsp;<br
/>-&gt; features&nbsp;<br
/>-&gt; description of how Plone is developped and can be used&nbsp;<br
/><br
/>A deicision maker could/might turn into:&nbsp;<br
/><br
/>----------------------<br
/><br
/><b>Plone end user:</b><br
/>- use a provided Plone system&nbsp;<br
/><br
/><b>Plone Administrator</b><br
/>- Webmaster, have through the web manage access&nbsp;<br
/>-&nbsp; Configure Add'ons&nbsp;<br
/>- help end users with using Plone&nbsp;<br
/><br
/><b>Plone integrator: someone who knows how to:</b><br
/>- Administrator&nbsp;<br
/>- install Plone&nbsp;<br
/>- Configure/webmaster plone&nbsp;<br
/>- Add some add'ons and use them&nbsp;<br
/><br
/><b>Plone themer:</b><br
/>- customise Plone&nbsp; Look and Feel&nbsp;<br
/>- knows a bit about the development process&nbsp;<br
/><br
/><b>Plone developer</b><br
/>- integrator +&nbsp;<br
/>- Develop plone-add'ons, do custom code modification&nbsp;<br
/>- Work on Plone Core&nbsp;<br
/><br
/><b>Plone solution provider:</b><br
/>- Sell <b>integrator</b> and/or <b>developer</b> and/or <b>theming</b> services to other internal or external customers.&nbsp;&nbsp;<br
/><br
/><br
/>-------------------------------------------------------------------------------<br
/>Friday afternoon july 30th:<br
/>Are these persona's / target groups happy at the moment or not and why? We do this to identify things that are missing for these persona's?<br
/>-------------<br
/><br
/><br
/>Try to write down a processes to get a feeling for them.&nbsp;<br
/><br
/>Release Process (bugfix release 5.0.X)&nbsp;<br
/><ul><li><a href="http://docs.plone.org/develop/coredev/docs/release.html">http://docs.plone.org/develop/coredev/docs/release.html</a></li
><li>release manager gets feeling there are enough fixes in the core packages to do a release</li
><li>look at the coredev sources.cfg and for every package that's in there, make an official release (&lt; release team)<ul><li>tag, test</li
><li>release</li
><li>upload to pypi</li></ul
></li
><li>make a pending release set on dist.plone.org (&lt; release manager)</li
><li>community members test the pending release and provide feedback</li
><li>community members suggest more packages that need releasing, add them to sources.cfg, go back:</li
><li>move pending release to official production soft-release (release manager)<ul><li>Trigger installer/build team to build a new release (&lt; build team)</li
><li>wait for official installers being ready, upload them&nbsp;</li></ul
></li
><li>Update version support information and hotfix pages (&lt; security team</li
><li>Create announcement for new release and update links to the latest release (&lt; communication)<br/><br
/><br/><br
/></li></ul
>What's not in the current proces:&nbsp;<br
/><ul><li>check if the documentation is still up to date<ul><li>Check if the robot-screenshots break (identifies UI changes)</li
><li>New features should be documented<br/><br
/><br/><br
/></li></ul
></li></ul
>semver versioning. bugfix releases should not contain any functionality changes.&nbsp;<br
/>minor release could contain functional changes/additions&nbsp;<br
/><br
/>---------<br
/><br
/>Release Process&nbsp; (Minor Release)&nbsp; 5.1)&nbsp;<br
/>What should be added compared to the bugfix release&nbsp;<br
/><ul><li>new features should be sanctionned and trigger by the framework team for a set of new features</li
><li>The documentation team has to review documentation for added functionality<ul><li>push out new version of the docs (new branch)</li></ul
></li
><li>The communication has to be involved to create higher level release info, press releases, social media messages</li></ul
>Try to come up with mechanisms to sync these involvements? Can the documentation stop a PLIP if the docs are missing? can the release manager release a minor version if the press release is not ready?&nbsp;<br
/><br
/><br
/><br
/>Major releases: (Plone 6)<br
/><br
/><ul><li>Have more frequent releases (not 3-4 year of waiting) so not everything is changed in one big major release -&gt; sticking to Semantic Versioning makes this mandatory</li
><li>If we do major releases, create a project(team) for this release and have a member of each normal team in this project team to coordinate the release<br/><br
/></li></ul
>---------<br
/>On saturday we found out these proceses are in some form written down in release notes in the github repository of the buildout.coredev account at <a href="https://github.com/plone/buildout.coredev/blob/5.1/docs/release.rst">https://github.com/plone/buildout.coredev/blob/5.1/docs/release.rst</a> , but this much more an extensive technical checklist and some of the interactions from/to other teams are missing. (which could be a cause of some of the quality control issues we have).&nbsp;<br
/><br
/>The Framework Team's PLIP process is written down quite extensive on Plone.org, (link needed here, it was shown), but parts of it seem not be be followed anymore.&nbsp;<br
/><br
/><br
/>------------------------------------------------------------------------------------------------<br
/>Written by a remote contributor friday/saturday july 30/31st. . Is this a 'should be' process, or an 'as is' process? Or a mix?<br
/><br
/><br
/>Roadmap process<br
/>- never written down.<br
/>- seems to involve having a confernce. having a discussion. Listing out what everyone has on their minds as features/major changes they would like to see or neccessary based on their own ideas.<br
/><br
/>One way it could work. Based on idea that we can be all things to everyone eventually but there is a limited amount of resources and some activities will help a community achieve its goals quicker than others.<br
/><br
/>1. Pick a vision of the community in 2020. How popular. specific numbers for each of the defined user types. Not what Plone he product will look like but what the community will look like.<br
/>2. Determine which users types need to be targeted first to achieve this goal. This is the most strategic part. For example, should integrators be the most important because they will choose the technology and end users often don't get a say? Should core developers be put first, since without them development will stop and everyone else will suffer?<br
/>3. Take the list of features/ideas/changes, For each feature determine which user type is affected and how they are affected using these categories.&nbsp;<br
/>&nbsp;&nbsp; - [wow] Something this user might switch to plone for. A USP. Something that demos well or makes a good headline. There won't be many of these.<br
/>&nbsp;&nbsp; - [doh] Something competitors have for that user type, that we don't have and its a deal breaker.<br
/>&nbsp;&nbsp; - [tick] Features that aren't used so otten but are normally on lists of things when decision makers and evaluating products and could negatively affect the decision to buy<br
/>&nbsp;&nbsp; - [smooth] features that are harder to describe or sell but make it easier to use. Things users can only appreciate once they are a user but will help in them recommending the product to others. Reduces support queries<br
/>&nbsp;&nbsp; - [power] features that you have to be a deep power user appreciate but can help those users enormously. There is normally a harder existing way to achieve this.<br
/>&nbsp;&nbsp; - [scale] features that increase performace or help with problems encountered when you run a very big site, or lots of sites.<br
/>&nbsp;4. Determine a priority of feature categories to achieve your goals. If community growth is the goal then it should probably be in the order above.<br
/>&nbsp;5. Sort the lst of features. Promote and publizes the priority order in the community. Help use that priority order to determine which sprints to make strategic.<br
/>&nbsp;6. Brainstorm missing features that fall into those categories.&nbsp;&nbsp;<br
/><br
/>At the end of this you will have a proper roadmap listed in priority order. Which is not to say thats how it will happen in reality, but at least everyone will know what the joint goal is and what the strategy is to get there.<br
/><br
/><br
/>----------------------------------------------------------------<br
/>Plone community processes continued discussion saturday morning:<br
/><br
/><ul><li>Continue with the process descriptions of the community<ul><li>only release process, or also security processes, community processes&nbsp;</li
><li>Flesh out the major release process more<br/><br
/></li></ul
></li
><li>How are we going to publish land this weekends sprint result up for further discussion in the community?<ul><li>release process<ul><li>we identified more teams that should be involved?</li
><li>discuss solutions to fix quality issues<ul><li>(plip cannot be approved before there's&nbsp; a documentation scaffold)</li></ul
></li
><li>teams vs. adhoc teams vs. projects<ul><li>plone.com minus design people should have been merged into communication team by now</li
><li>communication team is responsiable for plone.com</li></ul
></li
><li>merging of teams?<ul><li>accessibility with usability (do they really overlap? usability is often not about fine adjustments to exisitng features, but rather choose between 2-3 very different features requests to achieve the similar user goals. It's deciding how plone works. UX is not the default theme, or picking icons, or making something work with a screen reader).&nbsp;</li
><li>plone.org team will be resurrected to finish functionality and implement results of long discussions</li
><li>ask testing &amp; release team if they consider to merge</li
><li>'launch' team shouldn't be a team but a project-team that oversees the major release process</li
><li>project-team - task force / permanent-team&nbsp; / team- need to find some terminology for this.</li
><li>relabel AI-team -&gt; admin team? (Artificial Intelligence)</li></ul
></li></ul
></li
><li>Are there tasks that are missing, not done but don't belong to any team?<ul><li>vetting of incoming reports of users. Move issues to the correct repository?<ul><li><s>trac should become read only but also invisible for most users</s> -&gt; history team!</li
><li>distill 600 valid tickes from trac?&nbsp;<ul><li>ask admin team to give a trac copy to someone to extract these tickets</li></ul
></li></ul
></li></ul
></li
><li>Why are we not eating our own dog food and have a Plone dms space for storing sprint discussion results and other community produced documents?<ul><li>Not 'official' curated written documentation guidelines, but all the intermediary documents that are still interesting for&nbsp; posterity &amp; process</li
><li>Create a sprint content type to stop the 'create a sprint on coactivate' thing.<br/><br
/><br/><br
/></li></ul
></li></ul
></li></ul
>Generation of new features process<br
/>- PLIPs are toward the end of this process. Where does it start?<br
/>- Maybe it should be documented<br
/><br
/><br
/>---------------------------------------<br
/>P&amp;O Sprint friday morning 30th july. After creating the list of teams, what are the tasks that we currently know of that these teams are doing?<br
/><br
/>What is every team doing officially and unoffially?<br
/><br
/>Difficulties here:&nbsp;<br
/>-&gt; What were they doing, what are they doing, what should they doing, what do we think they are doing?<br
/>-&gt; We should validate this list in some way.<br
/><br
/>Plone Board:<br
/><ul><li>Brand</li
><li>Budget</li
><li>Conference selection</li
><li>Identifying Strategic sprints</li
><li>Intellectual property of the code / licensing</li
><li>Leading Marketing effort</li
><li>Plone Foundation Organisation</li
><li>Sponsorship for the central activities</li
><li>Liaison to Framework, Marketing and Security Teams<br/><br
/></li></ul
>Membership committee:<br
/>* Evaluate new member applications<br
/>* Recommends membership to the board<br
/><br
/><br
/>Framework Team:<br
/>* Evaluate and vote on PLIP's (PLone Improvement Proposals).<br
/>* Coach PLIP proposers to improve PLIP documents before they are accepted.<br
/>* Delegate proposer to other teams like UI/UX or Documentation.<br
/>* Review PLIPs with heavy impact on Plone<br
/>* Decide when to include a PLIP (Major, Minor, Bugix) - stick to semantic versioning as good as possible.<br
/>* Technically Merge the PLIP branch into the code repository<br
/>* PLIP process documented here: <a href="http://docs.plone.org/develop/coredev/docs/plips.html">http://docs.plone.org/develop/coredev/docs/plips.html</a><br
/>* Discuss incoming Pull Requests if they need to go through PLIP process or not.<br
/>* push release manager to do releases, coordinate releases with PLIP merges.&nbsp;<br
/>* coordinate with release manager to cut new branches for Plones next minor/major releases (this is the most complex task and needs coordination with testing team and documentation team, the exact process of this is not defined).<br
/>* helps release manager with new-features list on major releases<br
/><br
/>Training Team:<br
/>* Developing training material<br
/>* Organising the PloneConf Training days<br
/><br
/>Communication Team aka Marketing Team:<br
/>* Manage&nbsp; Plone social media accounts<br
/>* Write Press releases<br
/>* Create Physical Marketing Material&nbsp; (Tshirts, flyers, posters, booklets )<br
/>* Write Plone.com content<br
/><br
/>Documentation Team:<br
/>* Manage docs.plone.org technical setup<br
/>* Managing the release of Documentation Versions<br
/>* Writing guidelines on how the documentation should be written<br
/>* Documentation Quality Control<br
/>* Advise on Documentation Present<br
/><br
/><br
/>Installer Team:<br
/>* Create the universal Installers for Plone<br
/>* Maintain Docker/Vagrant setups for Plone<br
/>* Ansible playbooks?&nbsp;<br
/><br
/>Testing Team:<br
/>* manage the testing software servers (Jenkins Server),<br
/>* Give guidelines on what testing software should be used, best practices<br
/><br
/>Release Team:<br
/>* Release and push all the software packages on pypi that comprise Plone the Product<br
/>&nbsp;&nbsp;&nbsp; * Tags on github for each repository of the plone core packages<br
/>&nbsp;&nbsp;&nbsp; * Managing the coredev buildouts<br
/>* Coordinate with or assume the duties of the Launch Team?<br
/><br
/>Security Team:<br
/>* Issue patches for security issue in Plone<br
/>* Evaluate incoming Security issues/ Bug reports<br
/>* Do code evaulation on Plone Core and 'selected' add'ons<br
/>&nbsp;&nbsp;&nbsp; -&gt; (which add'ons are 'selected?)<br
/><br
/>Admin and Infrastructure (AI)-Team:&nbsp;<br
/>* Manage Plone Infrastructure, the servers on which the official sites run<br
/>* the mailinglists.<br
/>* RC-Channels.&nbsp;<br
/>* community.plone.org software install &amp; updates<br
/><br
/><br
/>I18n Team:<br
/>* manage plone.app.locales<br
/>* manage Transifex account (?)<br
/><br
/>Usability Team (formar aka UX team):<br
/>* Design and decide on end user experience of Plone the product<br
/>-&gt; Both Visual and Textual<br
/>-&gt; Some overlap with accessibility Team<br
/>* Audit the Official Plone theme (Barceloneta)&nbsp; for responsiveness, mobile, browser Support<br
/>djay: deciding end user experience effectively means deciding on features and its not clear how that works in practice. Plips are done by those that care. How can the UX team tell people what to do? More thought needs to be put into roadmap, features and how stuff really gets decided in plone to come up with something more pragmatic.&nbsp;<br
/><br
/>Accessibility Team:<br
/>* Audit Plone for accessibility Issues<br
/>* Maintain a resource list on Accessibilty documentation &amp; best practices<br
/><br
/>Plone.org Team:<br
/>did:<br
/>* design the new plone.org visual theme and features<br
/>does:<br
/>* Develop functionality for the plone.org website<br
/>* Writes some of the 'framework' content that doesn't change<br
/>* structuring of the content<br
/>-&gt; Most of the content should be community generated<br
/>Partly efforts are ad-hoc. / Overlap with documentation team<br
/><br
/>Plone.com Team:<br
/>* Was an adhoc team to create the new plone.com website.&nbsp;<br
/>* Mostly merged with the Marketing Team<br
/>* Develop functionality for the plone.com website<br
/><br
/>Launch Team: (adhoc, not really a team, trying to bundle other teams)<br
/>* Coordinate docs, training, marketing, and release of software&nbsp;&nbsp;&nbsp;&nbsp;<br
/><br
/>Ploneconf "Team"<br
/>*&nbsp;<br
/><br
/>=====================<br
/>Brainstorm Stuff:<br
/><br
/>Teams we should have:<br
/>* Onboarding team<br
/>* history-team<br
/>* Process troll team (we are!!!)<br
/><br
/><br
/>--------------<br
/><br
/>Who is managing?<br
/>* The Slack channel? (Kim, Jean Jordaan)<br
/>* Planet.plone.org? (that's clear: it's a github repository, just open a pull request to have your blog added)<br
/>* paragon (once we have the new add-on thing going, it can go to the big /dev/null in the sky)<br
/>* ploneconf.org and subdomains (AI team)<br
/>* plonesymp.org and subdomains (AI team?)<br
/>* YouTube Plone channel?<br
/><br
/><br
/>-----------<br
/>Saturday afternoon, discussion on the add'ons story (aka paragon, aka PSC replacement)<br
/><br
/>How to find add'on on plone.org<br
/>* only link is in doormat on the start page (<a href="https://pypi.python.org/pypi?:action=browse&c=589)">https://pypi.python.org/pypi?:action=browse&amp;c=589)</a><br
/>* the big blue 'add-ons' text below the hero banner isn't clickable ...<br
/><br
/>The link in the doormat links to pypi, but the pypi trove classifiers cannot discriminate between core plone packages, buildout or framework/testing packages and 'real' user addable add'ons.&nbsp;<br
/>We might need an extra trove classifier for 'genuine' Plone product add'ons.<br
/><br
/>then you can search for :<br
/><br
/>Framework :: Plone :: <b>AddOn</b><br
/>&amp;&amp; (union)<br
/>Framework :: Plone :: 5.0<br
/><br
/>Or we could use an existing general trove classifier like: "Environment :: Plugins" .&nbsp;&nbsp; All classifiers: <a href="https://pypi.python.org/pypi?%3Aaction=list_classifiers">https://pypi.python.org/pypi?%3Aaction=list_classifiers</a><br
/><br
/>Other useful trove classifiers:<br
/>Development Status :: 5 - Production/Stable<br
/><br
/>We have to ask all plugin releasers to add the Plugins classifier to their pypi packages.<br
/>* You have to put it in the setup.py<br
/>* It's possible for owners to add classifiers on already released packages as well.<br
/>* Add the classifier to bobtemplates<br
/><br
/>Ask for warehouse to be able to AND trove classifiers. Warehouse already looks much nicer.&nbsp;<br
/><br
/>Support curated lists? Can we add hand picked ad'ons on top of the pypi trove classified full list?<br
/><br
/>ideas behind orginal paragon:<br
/>- opionated. not have a public voting on popularity<br
/>- not be exhaustive, max 50-60<br
/>- to specifically not include low level developer add'ons.<br
/>- add tags for classification<br
/>- entry barrier: README, some documentation<br
/>- bonus points for including screenshots and other meta info when submitting an add'on<br
/><br
/>Target groups for paragon info:<br
/><br
/>* Newbie Plone administrators/integrators that want to test/add some add'ons to their Plone site for the first time. This should be as seamless as possible.<br
/><br
/>* Long time Plone users that come back to Plone in a new version and are looking for 'new' Add'ons to extend their site.<br
/><br
/>KISS principle? Start with a normal Plone page where we list the add'ons?&nbsp; Already is there but doesn't work, cannot present information like Plone&nbsp; versions. and tags/categories.<br
/><br
/>------------------------------------------------------<br
/>We probably want curated tags. Have some selected 'categories' as tags.&nbsp;<br
/>Add minor single dot versions. 4.3, 5.0, 5.1&nbsp;<br
/>name of the package&nbsp;<br
/>nice description<br
/><br
/>* Should descriptions be pulled from the pypi information or be hand crafted/separate and editable. &lt;&gt; Then you can ask a copywriter to improve the description.<br
/>* Pull other info from pypi like docs link etc. Alexander will look into this<br
/><br
/>----------<br
/>Create a page that can dynamically pulls in a list of add'on packages from pypi and put it in a datatable of some kind with pagination and selectable classifiers.&nbsp;<br
/><br
/>djay: alternative is using automated phone home system to get stats on what is used in production and what is compatible with which plone version. Helps add tags to plugins on plone.org on which is plone 5 compatible.<br
/>Another alternative would be phone home system in travis builds to record when a plugin passes for plone version X and display that as a tag on plone.org.<br
/>- idea is to not rely so much on individual&nbsp;<br
/><br
/><br
/><br
/>-----------------------------------------------------------------------------------------<br
/>P&amp;O Sprint saturday afternoon july 31st.&nbsp;<br
/><br
/>Discussion of the plone.org download and hotfix pages.&nbsp; (see task list at the top of this doc)<br
/><br
/><br
/>Plone.org downloads page&nbsp; &amp; download directions on the homepage<br
/>homepage<br
/><br
/>* 'Older releases' directly throws you off the Plone site to launchpad. It should link to a subpage (probably downloads page) where we have an 'older releases' section where we explain why you might need to download Plone instead of the preferred Plone 5.<br
/><br
/>* The download page has two similar Call to Action buttons for Both Plone 5 and Plone 4. We want prospects to download Plone 5!. We should move the 4.3 button down the page to a separate section where we explain why people would want to try out Plone 4.3 (Because their organisation still uses Plone 4.3 sites and they want to experiment.<br
/><br
/>Below the Plone 5 button we can put a line with a link to the 4.3 section.&nbsp;<br
/><br
/>* Link to the plone-announce mailinglist. Can we also add a @plone-announce twitter account where officeal release and security announcements are made?&nbsp;<br
/><br
/>For end/first time users it might be confusing and scare them to have big hotfix banners on the download page where they haven't even installed the product yet. And we could make these banners dynamix because we know when a hotfix is needed for which release. -&gt; Alexander will look at this, Installer team will discuss releasing updated installers when bugfixes come in so latest 'stable' and 'oldstable' have all relevant hotfixes included.<br
/><br
/>Another idea: it's not that hard to add hotfix releases to the universal installer, then we don't need these warning on the most recents (supported) Universal installer downloads at all. -&gt; see one paragraph up<br
/><br
/>If you think of three Plone target groups/persona's like&nbsp;<br
/>* newbies, want to try out plone<br
/>* beginning/intermediate user, is there an update for my system<br
/>* expert user, I install Plone form source.<br
/><br
/>And then look at the downloads/hotfix pages, sometimes one of these persona's is undervalued/not catered for. Many pages have little newbie info or guidance, and are overly complex.<br
/><br
/><br
/><br
/><br
/><br
/><br
/><br
/><br
/><br
/><br
/><br
/><br
/><br
/><br
/><br
/><br
/></body>
</html>