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

Question. Naming rules for self-implemented features. #1247

Open
ghost opened this issue Jan 16, 2024 · 1 comment
Open

Question. Naming rules for self-implemented features. #1247

ghost opened this issue Jan 16, 2024 · 1 comment

Comments

@ghost
Copy link

ghost commented Jan 16, 2024

Hello,

I would like to implement a simple XmlReader/XmlWritter that reads a table from a file and provides the functionality to save it.
For simplicity and easiness of use, a standalone jar is the preferrable way instead of forking the whole project. In this case, a user would be able to simply install the jar locally and use it together with the maven version of tablesaw, without the necessity to build the forked project.

If possible, I would also like to share the work on github under the same conditions as the tablesaw itself. However, I am not 100% sure about a suitable name for the project. For me, the most logical way seems to name the jar tablesawxml.jar, while the package will be something like alxsrs.tablesawplugins.tablesawxml.

Could you please tell me if the usage of this name would be acceptable for a custom project? Please feel free to suggest any ideas in case they seem more appropriate to you.

Thank you in advance for the help.

@frankwondon
Copy link

frankwondon commented Jan 16, 2024 via email

@ghost ghost changed the title Question. Naming rules for self-implemented issues. Question. Naming rules for self-implemented features. Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant