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

Mailinglist down #52

Open
toeklk opened this issue Sep 13, 2018 · 3 comments
Open

Mailinglist down #52

toeklk opened this issue Sep 13, 2018 · 3 comments

Comments

@toeklk
Copy link
Collaborator

toeklk commented Sep 13, 2018

It seems like the mailinglist is down...

http://lists.mech.kuleuven.be/mailman/listinfo/bfl/

image

@toeklk
Copy link
Collaborator Author

toeklk commented Sep 14, 2018

Not a temporary problem...

@meyerj
Copy link
Member

meyerj commented Sep 3, 2020

The KU Leuven mailing list infrastructure has been updated. The new ListServ URL is https://ls.kuleuven.be/cgi-bin/wa?A0=BFL.

We (at Intermodalics) are currently working on a new Orocos documentation page at https://docs.orocos.org and also a new minimal landing page to replace https://www.orocos.org. The documentation page also has a section for BFL, with pointers to existing API documentation. Feel free to contribute!

We also at least consider to close the orocos-dev and orocos-users mailing lists, and either stick to GitHub issues and pull requests only, or use ROS Discourse (see this mailing or the respective Discourse thread). Any preference for BFL, @tdelaet or @toeklk ?

@toeklk
Copy link
Collaborator Author

toeklk commented Sep 3, 2020

Hi Johannes, My 2 cents, in order of decreasing importance:
1/ I think it would make sense to have the same choice for all orocos subprojects
2/ I'm not familiar with ROS discourse, I think github issues work pretty fine (though IMO we must take care to indeed create a separate repository in order not to pollute the real BFL repository with issues that are no issues. But I have the feeling we are on the same lines there. I think most BFL users will have a github account, but not necessarily a ROS discourse account, so this prevents the need for yet-another-account

Yet, I have no strong opinion on the matter and, as mentioned, I think 1/ is more important than 2/

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

2 participants