Open drewjbartlett opened 6 years ago
@mgred let's use this as a base right now. We can work off develop
and make small pull requests against it while we are working. How would be best for me to delegate detailed tasks to you?
It might be good to use some of the github templating if you would like people to follow contributing guidelines.
https://blog.github.com/2016-02-17-issue-and-pull-request-templates/
@drewjbartlett cool plan.
Only submit small pull requests that are specific to the task
I like that workflow, think its quite efficient to do small but qualitative steps
How would be best for me to delegate detailed tasks to you?
You can give me any task, with a short description in an issue, I think that's enough BTW, does this list has any priority order?
@ctsstc @mgred I am down to use issues with templates. Also, there is no priority order on that list at the moment. I have taken on a handful of those tasks at the moment. I will break them up and delegate to you guys if you're down
Version 2 Checklist
Documentation
Fixes
Enhancements
api
renamed tohttp
apiConfig
tohttpConfig
qs
forqs-stringify
since we only use that method https://www.npmjs.com/package/qs-stringify.default
helper to go withmodel
/collection
photo.get('/tags', { order: orders.ASC })
.js
filesdeepmerge
instead of lodashwithData
towithConfig
qs-stringify
with old debuggeraxios
entirelyhttpConfig
from configdebug
from configBuild
prepublish
hook and replace with: Useprepare
for build steps andprepublishOnly
for upload-only.Tests
model
,collection
,default
I can add a contributing guide for this. But for now:
npm run unit:watch
while working on new features and fixes. Do you best to make small changes while always keeping the tests green.For now we can use issues or projects. @mgred I have not used projects for this but we can look into it!