Project Maintenance

[xloem]

It looks like this project may not be maintained at the moment. Is anybody interested in merging pull requests into a fork, discussing future steps, or setting up a github organization to collect effort together?

@jminardi @DerAndere1 @fake-name @lukasfeckl @qabacus @RobWks @rtellez700 @DanielSimone @leethomason @peets @razeh

[fake-name]

I may be able to help a bit.

My issue is that the interest I had in this project was motivated entirely by the need to use it for a single project at work, which is now complete. My professional work is highly varied and project-oriented, and once a project is done I may never return to it.

This leads to a lot of "drive-by PRs", where I effectively have no funding for revisiting a library/PR more then a few weeks after I make it. I also may not have loked at the code in question since shortly after the PR, which doesn't help with responding to questions months after the PR is opened.

[jminardi]

Hi all, I apologize for neglecting this project. I am willing to add maintainers to this project here or transfer ownership to an organization.

[rtellez700]

Since folks from the Lewis Lab are currently the main users of this package, I think it would make most sense for us to make a Lewis Lab GitHub and transfer ownership to it. Let me know y'all think.

[xloem]

To update this thread on my end (which i mentioned on rtellez’s repository earlier), after I opened this issue I ended up forking mecode to https://github.com/xloem/wheecode , merging in other forks, getting test infrastructure passing, and enabling automated pr merging. This was 3 weeks ago when I didn’t know whether any of you would respond, the commit renaming it could be reverted. EDIT: If the lab that developed this is still using it and has capacity to maintain it that would be great.

[jminardi]

@xloem I have added you as a maintainer for this repo. I don't think there is anyone at the Lewis Lab right now who would be able to maintain this. Feel free to add other collaborators who you have worked with previously on your fork.

[xloem]

I’m honored to be on the main repo and can likely find a time to bring my changes back here over coming months.

I do only see a 3d printer pretty rarely and similarly have rare time for this project; if anybody else is interested in committing here pipe up and we’ll add you.

[jminardi]

@rtellez700 Are you currently at the Lewis Lab now? Does the Lewis Lab have a GitHub organization? I know when I was there we had a private org but I am not sure if anyone uses it anymore.

[rtellez700]

@jminardi Yea I'm currently a graduate student in the lab. I'm currently working on getting the login info for the Lab's GitHub

[xloem]

I looked to see if I could add rtellez700 to this repository, but I don't seem to have access to add further contributors I'm afraid. I didn't work with rtellez700 making my fork, I simply forked rtellez700's repository, which is itself forked from RobWks' repository. I removed the 'whee' from my code and opened #79 to show the changes I made.

To publish new versions of this package, we'll need some kind of access to jminardi's pypi project, whether that's API keys, or somebody being added as a contributor to it, or jminardi doing the publish when asked.

[rtellez700]

@jminardi Hi Jack-- It took us a while but we are now in the process of updating our new Lewis Lab organization. Would you be able to transfer ownership of this repo to https://github.com/harvard-lewis-lab ?

[rtellez700]

@jminardi -- Hi jack just following up to see if you're still able to transfer ownership of this repo to the lewis lab?

[joansalasoler]

Hey,

I'm developing a plugin for vpype to generate G-code programs from .svg documents. For now, I'm calling it vpype-mecode [1] because one of the main goals of the project is to integrate mecode as a core component. This will provide users with a powerful and easy-to-use tool for generating G-code.

Over the past few weeks, I've been gradually extending the library and making breaking changes. I was wondering if anyone would be interested in integrating some of these changes into mecode. However, to be honest, I'm a bit unsure about who is currently maintaining the codebase or where it's being managed.

Does anyone know who is responsible for maintaining mecode or where contributions should be directed?

[1] https://vpype-mecode.readthedocs.io/

[rtellez700]

Hi @joansalasoler -- Happy to help! We still have not been able to migrate mecode over to our lab's github account. However, I have been maintaining the codebase under the my fork: https://github.com/rtellez700/mecode.

Feel free to open up a pull request on my fork, or if you want to discuss further you can open up a new discussion (https://github.com/rtellez700/mecode/discussions) to chat about what you would like to see implemented into mecode.

[joansalasoler]

Hi @rtellez700, thanks for the info! It looks like our codebases have diverged quite a bit, so I’ll start by merging some of your changes first. From there, we can continue the conversation.

In the meantime, you can check out the GBuilder class documentation, where most of my changes have been implemented, to see if the direction I’m taking aligns with the project's interests:
https://vpype-mecode.readthedocs.io/en/latest/api/vpype_mecode.renderer.html#vpype_mecode.renderer.GBuilder

[joansalasoler]

Hey everyone,

Just wanted to follow up on this thread. After I posted last month, I actually merged some of the changes I had been working on into @rtellez700 fork. You can find that work here: https://github.com/joansalasoler/mecode/tree/chore/vpype-mecode.

However, as I went deeper, I realized the original structure wasn't quite fitting the direction I needed, both for maintainability and flexibility, so I made the decision to start fresh. The result is a new project called Gscrib, which is licensed under GPL: https://github.com/joansalasoler/gscrib.

Hope this doesn't come across the wrong way. I really appreciate all the work that's gone into mecode. I wanted to mention it here just to be transparent about where my work led. My intention has never been to split off for the sake of competition, but to tackle some challenges that called for a rethink.

Thanks again to everyone for keeping this project alive!