Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

better approach to managing this project needed #32

Open
timabell opened this issue Oct 28, 2015 · 5 comments
Open

better approach to managing this project needed #32

timabell opened this issue Oct 28, 2015 · 5 comments
Labels
help wanted

Comments

@timabell
Copy link
Member

call for ideas!

although I've promised to keep this project alive and accept pull requests, I don't have the time / resources to properly review and test them myself. I wonder if there's a way of allowing the most interested / capable people to contribute without me having to decide on a whim who gets the "commit bit"

please pile in here with thoughts as I feel like it's starting to stagnate already
@timabell
Copy link
Member Author

This might help https://gitter.im/timabell/msaccess-vcs-integration

what do you think all?

@timabell
Copy link
Member Author

commit access now given to @jwbrookes @mgrojo & @dramosr (thanks for the contributions) so can all now handle PRs too

@timabell
Copy link
Member Author

added @bkidwell - the original repo owner :-)

@timabell
Copy link
Member Author

and @matonb who's contributed a fair bit too.

been looking at https://github.com/timabell/msaccess-vcs-integration/graphs/contributors if you're wondering

@timabell timabell mentioned this issue Mar 16, 2016
Open
@timabell
Copy link
Member Author

timabell commented Jun 3, 2017

I could spend more time maintaining this project with funding: https://www.patreon.com/timabell

@timabell timabell mentioned this issue Aug 6, 2017
Open
effjot pushed a commit to effjot/msaccess-vcs-integration that referenced this issue Sep 17, 2020
Get*Project should always return something
81700cd 
Use the same logic for GetCodeVBProject and GetVBProjectForCurrentDB
Use FSO.BuildPath to fix Log file path (remove redundant slash)
Handle HelpContextId errors, Closes msaccess-vcs-integration#32
Use `With` pattern to automatically handle objects
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@timabell