abeverley
commented
9 years ago I'd like to express an interest in this. Like you, I'm not able to dedicate any significant time, but I do use this plugin for a variety of projects, and it would be a shame to see it going stale. I also do not have much javascript experience, but hey, everyone needs to learn at some point ;-)
At the moment I'm working on a fix for a bug that causes problems when typing a date into a daterange. The main problem I'm having is understanding why something has been coded, so it would be useful if you were available to state the reason and give guidance. So if that's possible, what's the best way of me asking you? I don't want to open yet another issue for obvious reasons. Once I've got an answer I'll try to submit a suitable pull request.
eternicode
acrobat
hebbet
lukeocodes
Azaret
Eonasdan
vsn4ik
It's been well over a year since I last worked on this; issues, pull requests, and comments have piled up; and I don't see myself returning to work on it anytime soon.
So I'm opening the repo.
Developers
If you want to work on bootstrap-datepicker, comment here. I'll add you as a contributor, so you can push code and manage issues/PRs. If you only want to work on one section (eg, cleaning up the tickets), I'm cool with that. (I, of course, reserve the right to not grant access for whatever reason, but I doubt that I'll find many such reasons. :wink: )
Ideally, I'd like to get 5-10 people to start with. Ultimately, I'd like to add any person who has a decent-looking pull request, a la this article. But, for now, baby steps :sweat_smile:. For the foreseeable future, I will probably not serve any significant role in development -- I may pop in for discussion or to add contributors, but I will probably not work with the code very much.
To be clear, I'm not looking for new "project owners". At least not yet. I just want to bring the project out of stagnancy.
Rules
I would really only have one rule: don't merge your own changes. Multiple eyes on the code is the whole point of open source. Create an appropriately-named branch in the repo, submit a pull request on that branch, and have someone else review and sign off on it (I wouldn't have any restrictions on who merged it once it's signed off by at least a second person). Obviously there may arise a situation where a single person is maintaining things, so if a PR went weeks without a signoff, the contributor could merge it. But try to get feedback if possible.
License
I would hope it's obvious, but by pushing code to this repo, you would agree to release that code according to the license under which the project is released. Currently that's the Apache 2 license. If that license should be changed, that should happen sooner than later, as every contributor has to be contacted for such a change. Bootstrap themselves moved from Apache 2 to MIT, which would be my preference, and their issue twbs/bootstrap#2054 should serve as a template for how to go about relicensing.
Goals
I have some things I'd like to see done, but (obviously) haven't had the time to do myself. The community may ultimately decide some other path, which is fine, but this will serve as an acceptable starting point:
Goals for the repo -- these probably go without saying, but I will say them anyway:
Goals for the project:
Questions?
This issue should also serve as discussion of any questions or suggestions you might have about this process.
Let's do this.