[Help wanted] v1.0

[stavro]

Path to v1.0

The Elixir ecosystem will only be as good as the community which surrounds it! That community is responsible for a thriving environment full of shared knowledge, libraries, and enthusiasm.

There's clearly some amazing interest from the community in a solid file upload and attachment library, and Arc has filled that gap for many of you. However, it has some pretty rough edges, and doesn't always take the best functional approach.

While I don't have as much time as I wish I could dedicate to this project, I am enthusiastic about it and am certainly willing to drive the path forward. If anyone wants to help maintain this, leave a note here or in Elixir Slack and we can discuss the specifics.

Needed for 1.0

Close many of the outstanding issues, merge some of the PRs.

Some of the bigger ones:

• [ ] Extract S3 integration into a separate package
• [ ] Investigate combining Ecto
• [ ] Better / first-class ecto support. Eg. don't upload files from within the cast call
• [ ] Update file generation to match Phoenix v1.3+
• [ ] More logical filename handling
• [ ] Better UUID support

Anyway, let me know if anyone is interested in helping!

[joshchernoff]

Maybe a 1.1 but https://github.com/stavro/arc/issues/190 points out a very inserting problem to solve. What about adding a way to reprocess unloaders?

[lessless]

Hey @stavro,

I'm in the pre-release rush in the next month but really want to help. What do you think if I'll start from the looking on the PR's?

[ntietz]

Hey @stavro I'm interested in helping with this. I've submitted one PR ( #218 ) and noticed you seem to be pretty busy and might want help maintaining this. Let me know if you need anyone to look over PRs and help with that process.

[pedep]

bump @stavro I too would love to see arc evolve, and even though I'm probably not the best elixir developer yet, I would very much like to help out where i can - Do you see the possibility for members of the community helping drive development forward during periods when you are too busy being an option in the near future?

[ntietz]

It looks like we have a lot of users who want to keep arc moving forward, and no response from the maintainer. If we continue to get no response, maybe we should consider a fork?

[pedep]

I had the same thought (and maybe also host the project in an organization instead) Considering that the author seems to be active on github, judging by his recent contributions, i would like to give him the opportunity to respond Though some of you might have less patience than me, having waited what seems to be upwards of a year or more..

[stavro]

Even though there have certainly been people commenting saying they are interested in helping maintain, I’ve reached out to a few people and it ultimately went nowhere.

I’ll move this to an org and we can take it from there.

If you’re serious about wanting to help move this project forward then send me a message (stavro on irc or slack) - I’m awake and responsive during California daytime timezones.

For the sake of security, I’m not willing to give write access to the repo to anyone without a track record of quality elixir contributions, so understand that there may be a transition period where you provide feedback on PRs, open your own PRs, etc and I’ll merge it until such time where I’m confident it is in good hands.

-Sean

On Tue, Dec 12, 2017 at 8:15 AM pedep notifications@github.com wrote:

I had the same thought (and maybe also host the project in an organization instead) Though, considering that the author seems to be active on github, judging by his recent contributions, i would like to give him the opportunity to respond Though some of you might have less patience than me, having waited what seems to be upwards of a year or more..

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/stavro/arc/issues/189#issuecomment-351100832, or mute the thread https://github.com/notifications/unsubscribe-auth/ACR-INfDVjeKqI7tLFwEQ9TPnd1WP_atks5s_qargaJpZM4NWT0l .

[lessless]

Thanks, Sean!

On Wed, Dec 13, 2017 at 12:31 AM, Sean Stavropoulos < notifications@github.com> wrote:

Even though there have certainly been people commenting saying they are interested in helping maintain, I’ve reached out to a few people and it ultimately went nowhere.

I’ll move this to an org and we can take it from there.

If you’re serious about wanting to help move this project forward then send me a message (stavro on irc or slack) - I’m awake and responsive during California daytime timezones.

For the sake of security, I’m not willing to give write access to the repo to anyone without a track record of quality elixir contributions, so understand that there may be a transition period where you provide feedback on PRs, open your own PRs, etc and I’ll merge it until such time where I’m confident it is in good hands.

-Sean

On Tue, Dec 12, 2017 at 8:15 AM pedep notifications@github.com wrote:

I had the same thought (and maybe also host the project in an organization instead) Though, considering that the author seems to be active on github, judging by his recent contributions, i would like to give him the opportunity to respond Though some of you might have less patience than me, having waited what seems to be upwards of a year or more..

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/stavro/arc/issues/189#issuecomment-351100832, or mute the thread https://github.com/notifications/unsubscribe-auth/ACR- INfDVjeKqI7tLFwEQ9TPnd1WP_atks5s_qargaJpZM4NWT0l

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/stavro/arc/issues/189#issuecomment-351124978, or mute the thread https://github.com/notifications/unsubscribe-auth/ABd9zGHg46xUid415oqnOUZXBl9VLJfPks5s_rhZgaJpZM4NWT0l .

[ntietz]

One thing that would be helpful would be adding a contributor list or reviewer list so that folks like me can put appropriate reviewers on PRs, or know who to flag to do a merge once something is reviewed.

I tried reaching out to @stavro on Elixir slack and ultimately did not get a response (just "I'll get back to you in a few minutes") although I suspect he may have been busy at the time I reached out to him.