HackMD
Workgroup - Dev Community Facilitation
tags: workgroup
In every meeting: First 15 minutes Github Issues are checked
backlog:
- Show new stackoverflow questions in Slack #support
- last checked issue from oldest: #6671
04.11.2021
-
(Nicolai) adjust PR & Issue templates on all projects
- DONE
-
Status of search
- algolia
-
Determine release tags for
-
Testing -> download & test -> schedule it tightly
projects
- github stars (1k+)
- website
- release frequency - to check that it isn't dead & supports the latest libraries (django/python)
- the first page of the issues to see how well they're managed
- IM tool (slack, discord, matrix)
- who manages the development, ie not 1 person
- create headless mvp or a hybrid with another headless-like system
- no need to manage frontend
- (Improve UI of django CMS)
- fix frontend issues
21.10.2021
- Review survey (https://docs.google.com/forms/d/1j5FVT6xlwddKjJGJ-SGc2rHdQGP_Sg7oRopDs2l_-6c)
- Status of aldryn form
- we definetly need a form package in DCA
- workgroup description
- indicate that we're comfortable with a rewrite
- mention that the repository branch 6.0.x is up to date and has a lot of fixes
- ask @mishbahr whether he would like to merge (?) it with aldyrn-forms or move it django-cms org
12.10.2021
- (Nicolai) Scan PR to prepare next release
- First Issue with new template
30.09.2021
- (Nicolai) Amended the issue template -> https://github.com/django-cms/django-cms/issues/new?assignees=&labels=&template=–-bug-report.md&title=%5BBUG%5D
23.09.2021
- django-cms/README.md: add a note that it's a community-driven project
- we could redirect people from one group to another that is in a more dire need of their assistence
- Linkedin Profile or Github / CV
- ask for the tech experience by years (eg django 2y, react 1y, angular 0.5y, etc)
- we could try to approach people who have either contributed to the repository (through issues/PRs) or who maintain third-party packges. Those poeple most likely professionals, who are actively working on Django CMS, instead of filling in their time between jobs.
- we can add the relevant info to the template
- we could ask to join #workgroup-pr-review to confirm that a PR is welcome
20.08.2021
- Github Issue Management
- https://github.com/django-cms/django-cms/milestone/41
- Nicolai: reach out to Andrew and ask about status
- Design https://www.figma.com/file/qi2c8gInQNtU9LMdzslMrw/dCA-Website?node-id=0%3A1
- Website relaunch
- generic
- examples of their work, eg on github
- avaialability, eg h per week + long term
- other commitments
- eg if they have a full time job, or going to find a full time job
- long term goals
- eg if they are going to work with django-cms, or with python (backend) or frontend. or whether they simply do something in their free time
- fronted
- years of experience with frontend (bootstrap5)
- backend
- years of experience with django-cms
- generic
- Vacation handover
12.08.2021
- No topics, just Github issue management
05.08.2021
- last checked issue from oldest: #5742
- Review list of suggested labels
- Nicolai: I went through the issue management doc - it all seems very reasonable to me - not sure if anything needs to be changed regarding the process - wdyt?
- How can we improve the django CMS demo?
- brainstorming
- Results:
- Replace frontpage content with meaningful content about django CMS
- Add more content about django CMS to page
29.07.2021
- last checked issue from oldest: #5718
- headless CMS
- open source option:
- strapi.io
- wagtail 2.1
- commercial
- contentful
- primsic
- sanity
- open source option:
- another look at the docs & new user guide
22.07.2021
- Check Issue Guidelines for outdated content: https://docs.django-cms.org/en/latest/contributing/management.html
- Review test documentation: https://django-cms-doc-test.readthedocs.io/en/latest/
15.07.2021
- CKeditor5 announcement
- Last checked issue: #6987
08.07.2021
- create issue management workgroup
01.07.2021
- Victor and Nicolai to come up with proposal on how we can facilitate creation of "good first issue" on Github
- Make sure new design follows contrast guidelines https://image-color.com/color-contrast#A1C42C-FFFFFF
- Victor to recruit a new developer for CKeditor5 by making announcement in #contributors
17.06.2021
- Nicolai & Victor : Check google analytics and see which pages are most important -> create ranking
- Nicolai & Victor: Start with wireframing the most important pages in Miro
- Home (Nicolai)
- Features (Victor)
- …
10.06.2021
-
[All] Research & investigate django CMS competitor websites and present three must have features
- Nicolai to look at Statamic & https://plone.org
- Statamic:
- Fresh design, although a bit cluttered
- Home catered towards 3 main target groups with respective value propositions
- Feature page
- Documentation prominently featured -> Developer focus
- Get started page
- Plone:
- Statamic:
- Victor to look at Ghost.org & https://octobercms.com/
- Nicolai to look at Statamic & https://plone.org
-
[Nicolai] create first draft of sitemap in Miro
-
[Nicolai] create Figma account
03.06.2021
- [Nicolai] Link plugin page to getting started article & documentation
- link to documentation (Anatoliy)
- New Community Hero Page is live
- [Victor] link discourse to slack
20.05.2021
- [Nicolai] repositories and plugins page updates
- list of core (official) plugins: https://www.django-cms.org/en/blog/2019/01/29/django-cms-3-6-released/
- we can update the list based on the google sheet
- [Nicolai]
Add Github Stars to repos- Need help: https://ghbtns.com/#star
13.05.2021
- [Nicolai] Create wireframe for Community Hero list on website
06.05.2021
- Review Plugin categorization
29.04.2021
- Update: Zammad will be hosted by Andrzej
- Once completed -> Slack integration
- Update: Videos series django CMS for Django Developers by Vinits (planned)
- Update: Migrate Community Heros List to website -> Styling? -> wireframe
- django CMS website relaunch -> call to arms -> best approach?
- [Nicolai] Continue populating the work group subpage (ongoing)
- we can do fake pagination with CMS plugins when needed
22.04.2021
- [Victor] add google analytics v4
- [Nicolai] add gray background to work group page
- [Nicolai] research ticketing systems
- demo improvements
- UX-oriented content refactoring
- consider adding a chat box
- content specs google doc
- Check out django cms plugiins on github django cms site:github.com and try to come up with a categoriziation
14.04.2021
- [Victor] move https://gitlab.com/what-digital/django-cms.org/ to github
- make it private
- [Victor] work group page: try to add gray background
- [Nicolai] Adjust work group according to Victors changes
08.04.2021
Tasks
- [Victor] improve the work group page layout - add 3 columsn
01.04.2021
- mailchimp integration
Tasks
- [Victor] a page for community tasks
- [Nicolai] populate it with the content
25.03.2021
- new workgroup cards
- ready to be populated
- fix the menu on 1300px-
- create a ticket
- discord sync
- approved for a try
- ghost.org CMS platform review - this might be the main CMS on the open source market, but more of a wordpress direct competitor
- nice footer with CMS comparison tables, exactly what I wanted to find on my first visit
- their forum starts with a pinned welcome post - https://forum.ghost.org/t/welcome-to-the-ghost-community/8, where we could describe link our forum intro & community resources
Tasks
- [Victor] implement the HTML for the workgroup cards
- [Nicolai] populate it with the content
- [Nicolai] fix the menu on 1300px-
18.03.2021
- issues management - define labels, approve them through DCA, document the process, announce the need
- Kick off call with contributors + Andrew and Victor
- workgroup guidelines
- periodic calls
- enforce the tech brief specification
- Active workgroups:
- version 4.0
- CI
- CKEditor5
- Documentation
- Demo
- Multisite
- (PR Review)
- tech-marketing-workgroup
- posting about workgroup progress
- rust has a blog with new releases and upcoming features
- announcements
- keep an eye on the news
- eg once per month submit a set of arguments about
- business advancements
- cutting edge moderation system with easy to review and process versions
- file versioning
-
technical advancements
- business advancements
- posting about workgroup progress
- community contributors intros - posting it in text somewhere can help to reduce the need to reintroduce people in voice multiple times
- perhaps guidelines for the length, eg 2-3m per intro?
- New contributor slack channel #contributors
- How to make community tasks more "snackable" or "easy to pick up" ?
- How to make contribution more visible?
- Leaderboard? Contributor directory?
- currently:
- Leaderboard? Contributor directory?
Tasks
- Enable github discussions -> Nicolai to keep an eye on discussions
- Release call to arms announcement for PR work group
- Mark Walker, Anatolly, Simon stepped forward
- Change issue template (make them link to source directly) (Nicolai)
- [Victor] add slack notification in #support for the questions on discourse
- Posting on r/programming
11.03.2021
- workgroups page
- intro
- what skills do we need
- UX/UI, backend, frontend, full-stack
- what skills do we need
- cards
- name
- description
- people involved - count or names
- workgroup leader on a separate line - linked in link
- add the contributors on a single line
- resources
- tech brief - only the ones that are populated
- slack link
- goals/impact - why is it important, why is it great
- roadmap
- cta
- vacant roles
- needs
- intro
- link to the list of issues on github: filter by label and sort by upvotes
04.03.2021
- bring the workgroups to the website
- in progress
- configure CONTRIBUTING.md and make sure it's acknowledged by github
- review the issues once per month with the responsible people
- added to the tech committee agenda
- Change issue template (make them link to source directly)
- add slack notification in #support for the questions on discourse
- created a ticket on gitlab
- enable github discussions, consider moving the features there
