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.

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

Add OpenDeliveryBot to "Projects Using Mineflayer" #3162

Merged
merged 1 commit into from
Aug 25, 2023

Conversation

SilkePilon
Copy link
Contributor

OpenDeliveryBot is an ongoing project that is made in the python version of mineflayer. it allows players to use a bot to deliver items from place to place using a terminal CLI and GUI.

@frej4189
Copy link
Contributor

I don't think this project is big (or ambitious) enough to warrant an exclusive mention in the list

@SilkePilon
Copy link
Contributor Author

ik but its a good example of what can be done with the python version as there is no docs for it (not many)

@SilkePilon
Copy link
Contributor Author

also that list is a bit outdated:
"This project is no longer supported, check out the updated version at https://github.com/schematical/chaoscraft-mod"

@SilkePilon
Copy link
Contributor Author

i also plan on adding support for plugins. (in python)

Copy link
Member

@extremeheat extremeheat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, this list should be greatly expanded I think, there are many good projects not currently listed here.

@frej4189
Copy link
Contributor

I don't know.. there are literally tens of thousands of projects depending on Mineflayer at this point. I think it makes sense to have this list curated (and preferably not by the authors of those projects)

@extremeheat
Copy link
Member

Many dependents indeed, but a lot less functional end-to-end bots with docs. I don't think any gatekeeping is necessary beyond weeding out the obviously low quality/effort things. Authors are the ones writing the projects, so they've always been free to open PRs.

@frej4189
Copy link
Contributor

Sure. It makes sense that authors open the PR themselves. But it also makes sense that we don't have every single well-formed project in the list, because that would take up way too much space in the README. Maybe adding a projects.md could make sense.

For the projects in the README I think they should be remarkable in some respect. Either for their creative use of the library or for the sheer size of the project. But seeing as this list is definitely outdated it'd probably make sense to have a general discussion about what "requirements" should be needed for a project to be featured in the README.

I do not think this project fits, but that might just be me.

@extremeheat
Copy link
Member

Sure. It makes sense that authors open the PR themselves. But it also makes sense that we don't have every single well-formed project in the list, because that would take up way too much space in the README. Maybe adding a projects.md could make sense.

A projects.md could probably be added at some point yes. But I don't think the size of the current README is anything blocking for the moment.

For the projects in the README I think they should be remarkable in some respect. Either for their creative use of the library or for the sheer size of the project. But seeing as this list is definitely outdated it'd probably make sense to have a general discussion about what "requirements" should be needed for a project to be featured in the README.

So as you mention some things listed here are outdated. But I think they still have some historical significance like rbot, maybe an additional sublist for "outdated but interesting", maybe you want some inspiration?

Aside from weeding out the low quality/effort (things that could be examples)/done many times over projects, I disagree about nitpicking too much here to make listing here some competition. For code contributions this matters, as maintainers have to maintain code written by contributors and not understanding that code or it being low quality is added tech debt.

I do not think this project fits, but that might just be me.

Can you elaborate ? I don't understand.

@frej4189
Copy link
Contributor

I don't think the size of the current README is anything blocking for the moment.

Not currently, no. But it seems the last time the projects list was updated, there were only a couple hundreds projects depending on Mineflayer. Now there are over 25000 (counting only public repositories on GitHub). So my concern is if we add in any odd project to the list, it will quickly grow to be a major part of the README, which is not ideal.

I see your point about not favorizing some over the others which is why I think just sorting by popularity (say, number of stars on GitHub) would make sense. Then include something like a top 5 and have the rest in a different file and just link there.

The reason I don't think this project fits is that it is not very technically ambitious, it is not actually finished, and it seems to have no user base thus far. That does not make it a bad project by any means, but I don't think it makes sense "promoting" (can't find a better word) it in the main README of the project.

@SilkePilon
Copy link
Contributor Author

It's also meant as an example of the Python side of mineflayer. I've not seen many projects based on Python and the idea is that it shows what can be done with it (as the code is a bit different from JS). I needed to use the JS code as a base and use a tool to convert it into Python code to use as there is not much documentation for it.

as for the user base, it's hard promoting a GitHub project (for me then)

@frej4189
Copy link
Contributor

as for the user base, it's hard promoting a GitHub project (for me then)

This is my primary objection. I didn't want to say it because you hadn't explicitly stated your intent.

I don't think the projects list should be a way for authors to promote their projects. It's meant solely to emphasize the powers of the library with concrete applications.

Or at least that's how it should be, in my mind.

@SilkePilon
Copy link
Contributor Author

also, this project is using https://github.com/Textualize/textual
OpenDeliveryBot 19-8-2023 23_20_33

@SilkePilon
Copy link
Contributor Author

as for the user base, it's hard promoting a GitHub project (for me then)

This is my primary objection. I didn't want to say it because you hadn't explicitly stated your intent.

I don't think the projects list should be a way for authors to promote their projects. It's meant solely to emphasize the powers of the library with concrete applications.

Or at least that's how it should be, in my mind.

my intention is not to promote the project. only to show what the Python version can do.
I'm making some docs for it as well

@SilkePilon
Copy link
Contributor Author

will this be merged or is there gonna be a new system?

@SilkePilon
Copy link
Contributor Author

@extremeheat ?

@extremeheat
Copy link
Member

Important things I think are:

  • does it work?
  • is anyone using it ?
  • are there good docs?

On the last point I'd recommend listing the package on PyPI for ease of use, but that's up to you.

@SilkePilon
Copy link
Contributor Author

😄 I just added it to PyPi https://pypi.org/project/opendeliverybot/

  1. it does work but I'm working on making it better so some things may bug out.
  2. at the moment I can't see if someone is using it but it has 231 clones
  3. the Docs is a work in progress as I want to make the code work well before committing to writing the "full" docs.

im inplementig #3163 (if it works tho)

@SilkePilon
Copy link
Contributor Author

also someone is making a nice web based gui for it

@rom1504
Copy link
Member

rom1504 commented Aug 25, 2023

I'm going to merge since you're actively working on it, but yeah we should clean up the list of user projects

@rom1504 rom1504 merged commit ab3c0cf into PrismarineJS:master Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Closed
Development

Successfully merging this pull request may close these issues.

4 participants