search

SublimeGit / SublimeGit

Git integration for Sublime Text 2 and 3
https://sublimegit.readthedocs.io
MIT License
310 stars 50 forks source link

Proposal/Request for Ideas: SublimeGit Contribution Guidelines #234

Open sbuttgereit opened 7 years ago

sbuttgereit commented 7 years ago

In order to help keep this project transition to taking advantage of community support. I'd like to propose/solicit ideas for contribution guidelines. I have a set that I'll post that I use for my own projects, (editing them now as they're not completely suitable for this project, I'll post as a comment to this issue later), but if someone else has a good set of guidelines that are suitable for a project of this scope, it would be great to see those. As much as anything I see this as a safety valve from me unilaterally screwing things up and I'd love to encourage community support of this project. @miped your ideas, input, etc. are especially important as I still think of this as your baby (I didn't fine a good way to contact you prior to this post... there's an email in the repo, of course, but I don't want to presume that I get to contact you out of band).

Anyway, I wanted to get this up sooner than later; there are some pull requests in and issues on the table and I want to start getting things up-to-date.

miped commented 7 years ago

@sbuttgereit Feel free to contact me any time :-)

mikedehart commented 7 years ago

If you add a CONTRIBUTING section or md file to the project with details on contribution guidelines I'd be nice to include steps for a 'recommended' dev setup.

I've mostly worked on commandline or flask/django projects and just curious how @miped and others set up an ideal environment for testing ST2-3 plugins. I've gotten it working through ST3 but I don't think its an ideal situation heh and I haven't found a way to load through an IDE like Pycharm and still get the sublime dependencies loaded.

I'm glad this project still has legs though! 👍

miped commented 7 years ago

So here's what i've usually done: Basically symlink the development folder into the sublime packages folder. Develop in sublime text, restart sublime text, test. It kinda sucks because of all the restarts, but it definitely works.

mikedehart commented 7 years ago

@miped thanks for that :) I was cloning directly into the packages folder which was getting ugly. Not sure why I didn't use a symlink.

mmattes commented 7 years ago

I have added a sample CONTRIBUTING.md here #245, i think this is a good start for the project.