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

Should the project have its own website? #18

Open
LucianaMarques opened this issue Jan 9, 2019 · 5 comments
Open

Should the project have its own website? #18

LucianaMarques opened this issue Jan 9, 2019 · 5 comments

Comments

@LucianaMarques
Copy link

LucianaMarques commented Jan 9, 2019

I believe that the project should have its own website, preferably a simple one built with github pages. I think it's a good way to register activities, improvements and research on the field.

I would be happy to make this happen if approved :)

@RenatoGeh
Copy link
Owner

Sure. Feel free to make this happen. Any contributions are more than welcome. :)

Would this require us to move GoSPN to its own organization?

@LucianaMarques
Copy link
Author

I think you can create a page for the project, but by default it would be something like https://renatogeh.github.io/gospn and i'm not sure if we can switch it (see reference).

I believe that creating an organization could be good not only for hosting this site but also because in the future it may be interesting to create other relevant repositories apart from the core development, such as applications built with the framework. I'm not familiar enough with the project to give you a solid example of what could be done separately from this repository, but I believe this could somewhat help in the future from what I've seen with other projects.

@RenatoGeh
Copy link
Owner

You raise some interesting points. In fact, the TensorFlow integration issue (#19) fits quite well with your arguments. As mentioned in #19, TF still lacks several key API features for the Go module to be fully functional. So we might actually need to create a Python module to fill this gap.

As to the website, I'd prefer it not to rely on any new dependencies. I'm a stickler (and an annoying one at that) for pure HTML/CSS and JS. My argument for this is that we'll never have to depend on someone else's code nor will we have to download a bunch of trash to our OS's (I'm looking at you Jekyll). Plus, we get to learn how things are done without having yet another abstraction layer on top of it. I'm aware of the amount of work this would require of you, so I won't blame you if you don't want to take this.

Having said that, I'm always willing to change my mind if you provide me with some compelling arguments.

@LucianaMarques
Copy link
Author

Are we going to have an onganization then? :)

As for the website, I have a few suggestions apart from Jekyll! I'll gather them here. And I'm not afraid of doing what you said concerning the development in HTML/CSS and JS, but as I'm not a skilled web developer (yet), it may take some time.

@bruno-caldas
Copy link

bruno-caldas commented Jan 11, 2019 via email

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

3 participants