caktus / caktus/dsd-pythonanywhere
1.0 checklist
- Dominant language
- Python
- Stars
- 10
- Forks
- 5
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 5
Description
Hi @copelco! This is really cool to see. I've been curious what a PA plugin might look like for a long time, and it's really satisfying to see a working version.
I'm wondering if you've given any thought to what would be needed to make a 1.0 release. I've found it challenging to get this project into wider usage, in part because I think people see that these plugins are working for small projects, but they don't know how reliable the deployment process is for their own projects.
I'm heading a Djangonaut Space team over the next two months with a focus on django-simple-deploy. One of my goals for this session is to make a generic 1.0 checklist that any plugin developer can use as a guide. If you're interested, if might be helpful to hammer some of that out right here. I have a Scalingo plugin I need this for as well. If we can agree on a basic checklist, I'll drop it into the plugin generator so everyone can work from a consistent checklist.
Edit to add: I opened this issue to make a 1.0 release feel closer and more attainable, not to add any pressure around this work. I hope it comes across that way.
Broad tasks
---
- [x] Draft a generic 1.0 plugin checklist. (See [dsd-plugin-generator 33](https://github.com/django-simple-deploy/dsd-plugin-generator/issues/33))
- [ ] Supplement that with any PA-specific items.
- [x] Copy generic version to dsd-plugin-generator.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the generic 1.0 checklist referenced in dsd-plugin-generator issue 33, then compare it with this PythonAnywhere plugin's deployment concerns. Identify the remaining PythonAnywhere-specific checklist items and document them without duplicating the generic version; done means the supplement is complete and consistent with the copied checklist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100