Need New Lead

[nmccready]

Ok people I got too much going on. I maybe (maybe) have 2 more releases in me for this project. The main release being bugs and moving to ES6 #1575 .

The original intent for 3.0 was to become heavily config based similar to angular-leaflet-directive. It was also to support Angular2 (may be too aggressive).

Anyway someone needs to step in that wants to do the rewrite which can be 3.0. Cause I do not have plans to do it. Your first step in getting involved on this is making a PR for a new 3.0 branch, or letting me know about your fork to watch it develop. Then after I know you are serious; you will get perms to this repo.

If no one does chime in; I will be deprecating this project in favor possibly directing to ng-map or something else.

You have been warned.

[nmccready]

3.0 could also be a rewrite against Angular1.x as well with a migration path from 2.X .

[ZachMoreno]

Hello @nmccready,

Thank you for your hard work, contributions & time in maintaining the angular-google-maps project. I'm interested in assuming the role of lead, but I have some questions & minor concerns around this shift.

Questions

1. On average, how much time weekly do you spend contributing to & managing this project?
2. How active are the community members with discussions & PRs?
3. Can you please explain your/this project's relationship to AngularUI?
4. Aside from the project website, what are the primary means of community building?
5. How & when did you assume the lead role on this project?
   • Looks like @nlaplante was the original owner with the first commit on Aug 12, 2012
   • I see your 1st commit was on Jul 10, 2013

Concerns

1. I've never contributed to this project
   • I've put it to good use in multiple production apps & am therefore invested in it's long term success
2. I've never been the lead developer on an open source project of this scale
   • I'm the lead Web developer for a Ca. state agency
   • I've published an article & a book on Angular

[nmccready]

@ZachMoreno sorry for the delay, I have stopped watching this lib to keep the notifications down to a min. So I check things here and there.

Questions

On average, how much time weekly do you spend contributing to & managing this project?
- When I was active on this project I would spend 1-3 hours a night or every other night.
- 3-4 hours if not more on Saturdays or Sundays
- Keep in mind my work was using this lib at one point as well. This allowed some work hours.
- majority of it was on my own time
How active are the community members with discussions & PRs?
- active in creating issues and few and far in-between actually dig in and attempt to make fixes
Can you please explain your/this project's relationship to AngularUI?
In a nutshell @nlaplante was worn out as I am a now. We were looking to find a group to associate angular-google-maps. It just so happened that at the same time angular-ui was looking for a lib to replace angular-ui/map . They wanted to replace map for exact same reason there are issues now with angular-google-map. Lack of contributors and the maintainer wanting to move on.
Aside from the project website, what are the primary means of community building?
- gitter for public chat help
*- slack channel for all active admins and contributors. (basically people that consistently dig in and PR)
*- google plus community (though I do not watch it often at all)
- hangouts video chat and text
**
How & when did you assume the lead role on this project?
I started making main PRs to fix, and refactor much of the original library. I discussed with @nlaplante a lot and I was given push permissions. Once, we became part of angular-ui the group permissions are much more polished.
Looks like @nlaplante was the original owner with the first commit on Aug 12, 2012
Yes @nlaplante is the original owner and is still credited with a ton of the work.
I see your 1st commit was on Jul 10, 2013
Correct, why is this a problem?
Concerns

I've never contributed to this project
* - Start making PRs and or request to get into slack and we can discuss things one on one.*
**- I have had many people state they want to get involved but never really follow through. (No PRS or emails die off)
I've put it to good use in multiple production apps & am therefore invested in it's long term success
- Awesome, then you should have a decent idea of some of it works internally
I've never been the lead developer on an open source project of this scale
- Well then here is a opportunity to give it a shot and maybe do more than I could.
- Keep in mind that the amount of actual active devs that commit code are around 3-5
I'm the lead Web developer for a Ca. state agency
I've published an article & a book on Angular
- Cool, what book? URL?

If you want to discuss this offline please email me (which is provided in my account info).

[nmccready]

@cthrax @nlaplante @kandizzy @wrummler care to add any other comments?

[cthrax]

Just some things I think we've learned from the issues that have come through:

1. People seem to need example code for everything (we got halfway there with the example directive in the documentation)
2. People tend to shy away from digging into Coffeescript. We've had a number of PRs that are to the compiled JS and then they disappear when asked for coffeescript contributions. Don't get me wrong, working in coffeescript is a huge help in many cases, but people tend toward "not my language" IMO.
3. It is confusing for folks that we commit the compiled JS, a lot of PRs make the change, but not the recompile.
4. 80% of issues are submitted without any method of reproduction, so it makes a real burden to attempt to solve issues because the first question is always "Can you provide a plnkr demonstrating the issue?" and then we don't get a response in most cases, or code is copied and pasted into the issue, which is non-helpful.

So all that is to say, we tend to not get a lot of help, we get a LOT of issues filed and when we do get help, it tends to be difficult to integrate due to 2 and 3. So if I was looking for biggest bang for the buck, fixing 2 and 3 would be a huge help. Maybe being more judicious about closing non-exampled issues would help too, but after awhile you start to feel like a jerk. This repo tends to average 3-7 issues filed or commented on a day.

[kandizzy]

I will echo two things, people have a strong aversion to Coffeescript and generally do not provide reproducible examples even though we have this awesome explanation of how to do it.

I mostly support the search box directive. One of the biggest issues is its compatibility with other frameworks, like ionic. Since I don't use ionic, it is difficult for me to respond to those issues in a helpful way. Finding someone willing to support on ionic compatibility could reduce the volume of issues.

[eczajk1]

For me, the scope of this repo is the major obstacle. I wish I could help more, but there is no way I can keep up with all the issues people have with Markers, for example - because I don't use them.

It also seems like there are quite a few external dependencies, which I don't use but that seem to cause problems. I would think things would be more manageable if at least some of the individual components could be extracted into their own repo's (see #1764) and be implemented as optional "plugins".