Call For Maintainers

[JamesRamm]

When I start longclaw, I was running an e-commerce website and the marriage of wagtail with some basic e-commerce functionality perfectly met my needs for a lower cost than using a hosted solution.

Now, I work on totally different areas of the web and have no e-commerce interests and no time to keep this project going. Which is a shame, since I think there is a need for an e-commerce solution tightly integrated within Wagtail.

If anyone is interested in taking this project forward, please get in touch below. I am happy to add interested & active developers as full maintainers and/or move longclaw & related projects to their own Github org.

[sam-mi]

Hi James,

I'm using it in a project and would like to get it to support Django 3. I'd be happy to help maintain it along with anyone else who might like to help. I wont be able to give it a lot of time but hopefully it wont need a lot once its on 3.2

[JamesRamm]

@sam-mi I've invited you as a collaborator

[simo97]

Hi @sam-mi,

I am also using this project on several projects (with a friends). i would like to work on it also.

[JamesRamm]

@sam-mi @simo97 You have been added as collaborators to the repository - you'll need to accept the invite

[thenewguy]

I am still interested in this project as well

[sam-mi]

Salut James,

Apologies. I was away and the invitation has lapsed, would you mind re-inviting me when you have a moment?

[DarkArtek]

Hello, i'm interested too

[chrisbarry]

Hi James, I also could potentially help out, I'm very busy, but I could do what I can.

[tekanokhambane]

Hi James im also interested in being part of this project

[JamesRamm]

Hi @DarkArtek , @chrisbarry @tekanokhambane I have sent you invites to the repository

[sam-mi]

Hi James,

I wasn't able to get to the invitation in time, would you please resend it?

Thanks,

Sam

On Tue, May 18, 2021 at 4:26 PM James Ramm @.***> wrote:

@sam-mi https://github.com/sam-mi @simo97 https://github.com/simo97 You have been added as collaborators to the repository - you'll need to accept the invite

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/JamesRamm/longclaw/issues/375#issuecomment-842883987, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACBH3MJDNNN4JUXFJJINRPDTOICATANCNFSM42QS5X5Q .

[JamesRamm]

@sam-mi resent

[OneEyeDoll]

HI James, i'd like to help you mantain the project. Is there a TODO list?

[JamesRamm]

@OneEyeDoll, Still interested? TODO list == the issues board

[Xergon-sci]

@JamesRamm Are you still looking for maintainers? We would like to use longclaw in our projects, but it seems it needs some work done. I'd be happy to hop in on this and maybe some other team members in the future as well.

[JamesRamm]

@Xergon-sci Yes absolutely. I will send you an invite

[janbaykara]

Watching this issue, as my team is also interested in seeing this package resurrected. Have the volunteers in this thread managed to meet up and are there next steps / a roadmap of any kind yet?

[Whizfactor]

Well i am about to start a few ecommerce and multi-vendor projects so i did love to join so that the features I need are created and added to this repo. So @JamesRamm you can add me to the list. Thanks.

[janbaykara]

Hey all. I spoke to James on email and gained member status on the org. I can get PRs merged where they're needed but am not actively using this project. I just want to ensure that there's some movement on this important repo!

It would be good to get everyone together to figure out how we can collaborate. I don't have lots of experience with open source governance so I'm just spitballing here, but some next steps to me looks like:

The bare minimum

• [ ] Clean up issues — what are live issues, what aren't, duplicates, etc.
• [ ] Backlog of priority issues that means this repo can be spun up
  • [ ] Propose other issues to go in https://github.com/longclawshop/longclaw/milestone/10
  • [ ] E.g. propose issues that will get PRs working again (e.g. Travis CI — is this still usable, and what needs to be changed to make that work?)
• [ ] Review of forks of this repo that could be merged back in to solve some of the problems identified in these issues
  • Reach out to these maintainers to discuss this.

Long term repo health

• [ ] Identify a direction of travel past 'OK, it works'
  • [ ] Propose "what this is" / "what this is not" and other high level product / roadmap docs
  • [ ] Review the milestones and propose changes
• [ ] Set up some community governance. See https://github.com/longclawshop/longclaw/community
  • [ ] Create a code of conduct
  • [ ] Create issue template(s)
  • [ ] Create a pull request template(s)
  • [ ] Set up discussions section — @JamesRamm
  • [ ] Propose that more contributors get repo privileges
  • [ ] Propose some sort of release cadence + processes for getting stuff shipped

CC @sam-mi @simo97 @DarkArtek @chrisbarry @tekanokhambane @oneyedoll @xergon-sci @whizfactor: could any of you pick up any of these tasks, start making some issues / docs / proposals / PRs towards them? Or propose alternative ways forwards.

[chrisbarry]

Hey,

Thank you for doing this! I'm not sure I'm going to be help that much, but I have recently built a fairly large (600+ product variant site) and I would have some architectural thoughts that I learnt from doing this.

Essentually, I think I'd like to see a version of longclaw that is stripped back a bit, almost to a core first, which would include the most basic of things first (Basically the Product, ProductVariant & Cart functionality) and essentially just start with that, and then have other stuff / things added via extra dependencies or apps. Perhaps also having a route to starting without using the longclaw command (this probably already exists, but it can be a bit overbearing to see things having a templater, unless they are wagtail of course ;)

The reason for this is that in this project, I quite often found that I just wanted to implement some things myself or had to make the api conform to a pre-built frontend, so it was / is going to be easier just to do those things myself, so it would be nice to feel that long claw could get out of your way if you wanted it to..

TBH I didn't have any problem with anything in long claw (I'm not sure if carts should have their own model object, or just linking the items by session key as you've done is better, again, wasn't really a problem, I just might have had a cart object, but maybe that makes more of a mess!)

Perhaps also we should consider who is our key user? Is it someone who is experienced with wagtail, or might this be the first wagtail site they work with. Just a thing to consider about who the solution is aimed at.

[Hchenni]

Hello i m not a programmer but i can do some test to help

[damascene]

@janbaykara thank you for trying to help. I think the most important issue is that it's not possible to install Longclaw using the install guide. There is an issue with migrations: https://github.com/longclawshop/longclaw/issues/387

pip package seems to have some issue.

[JamesRamm]

Hi This call is still active. @chrisbarry seems to be the most active and I have given you maintainer rights. If anyone is using this project and would like to contribute, don't hesitate to get in touch.

[nickmoreton]

@JamesRamm Many thanks I have accepted the invitation 😄

[king-qamata]

Hi, James currently looking at integrating this with a project and wouldn't mind tagging along for the ride, especially being my first attempt on an open source colllaboration, thanks. ALso thanks for this great Repo

[janbaykara]

Hi all. My team's workload shifted and this no longer is a priority area for us, so I can be removed from the maintainer's list.