The oslc-community from oslc

oslc-community's Issues

Update the logo consistently throughout all materials

https://www.youtube.com/c/OpenServicesDotNet (#13)
open-services website
open-services Twitter
open-services Discourse
add logo to the http://www.wikiwand.com/en/Open_Services_for_Lifecycle_Collaboration ? (#12)
https://twitter.com/eclipselyo
https://www.eclipse.org/lyo/
https://www.linkedin.com/groups/3957829/profile
https://github.com/OSLC

please edit to add the forgotten places where the logo needs to be updated

Gracefully close down OSLC mailing lists

Once #1 is done, we should encourage the subscribers to move over:

OASIS for OSLC spec discussions
Discourse for general OSLC discussions
Github/Lyo for the implementation discussions

http://open-services.net/mailman/listinfo

Change Discourse Community Documents

Currently we have the following documents which are available to 'staff' only. Let's modify them and make them public, and delete the ones not needed.

FAQ/Guidelines
http://discourse.oslc.co/t/faq-guidelines/5/2

Discourse Categories

What categories and sub-categories should we have on Discourse?

Here are some initial suggestions

Announcements (admins can post only)
News
Software
- Tool Implementations
- Adaptors
Governance
Working Groups
(have working groups under as sub-categories)
Specifications

Any thoughts? @berezovskyi @rersie @jamsden @axelreichwein

10th Anniversary Branding Assets

We are ordering some special 10th anniversary merchandise to use at upcoming events. Initially these two items.

https://www.usimprints.com/product/travel-tote-luggage-tag-9184479/
https://www.usimprints.com/product/neoprene-portable-electronics-case-with-carabiner-10082865/technology

We will need the branding assets for the order. The creative idea we have is:

Logo + (Open Services for Lifecycle Collaboration)
Lifecycle Integration for the Web
10 Year Anniversary [or 10 Years (2007 - 2017)]
http://open-services.net

That might be a lot of fit on something small.

From their FAQ:

What art formats do you accept?
We prefer high quality vector artwork in .eps, .ai (adobe illustrator), with fonts converted to outlines. We may also accept high resolution .jpg, .gif, .psd, or .pdf files. We can fix your art for free!

cc @m257645 @rersch

Update Wikipedia Page

It is quite a bit dated now:

https://en.wikipedia.org/wiki/Open_Services_for_Lifecycle_Collaboration

Youtube Channel Art for OSLC

We have a Youtube channel at:

https://www.youtube.com/c/OpenServicesDotNet

Please produce a new banner / piece of channel art that will show on the page. It has to be at a larger size of 2560x1140 (recommended).

Github login on Discourse broken

When trying to sign up at discourse.oslc.co, there is an error.

Possible solution:
https://meta.discourse.org/t/how-to-solve-this-error-sorry-there-was-an-error-authorizing-your-account-perhaps-you-did-not-approve-authorization/32599/15

Updated Branding Assets

Determine what we need for our new Web properties (website, Discourse, ...), and produce the assets.

First off, we need logos. Note that we are tweaking the colours in issue #4.

We should put a little padding around new icons so that they center better. Right now the icon pushes right out to the edges.

Website - will defer to @gabrielfdac for determining what we need here.
Discourse - these are the logos we use currently, that will need to be redone. Note that the image + text logo is a hack that I did.

Logo url

Logo url small

Favicon url

Apple touch icon

OSLC logo colors tweak

Hello, I'm Gabriel and me and another developer called Hector are currently working on the new design for the OSLC site.

During our work we wanted to use the colors in the logo on some of the website, but we noticed the colors are a bit "washed" or dim, at least for a website.

So we proposed a slight tweak to the colors, the tone difference is small but enough to "brighten" up the logo and it allow us to use those colors throughout the website.

Please let me know what you think.

Discourse Setup

Setup OSLC Community Discourse instance.

Preference to have them live on sub-domains:
discourse.open-services.net

2 Options:

Self-hosting
https://meta.discourse.org/t/running-other-websites-on-the-same-machine-as-discourse/17247
Paid hosting

Things to consider:

Cost
Features being offered for each, e.g. email configuration
Install process
Path to upgrades + maintenance

TODO

Set up https
Enable registration via Github

Wiki Specifications Not Available All The Time

Problem

Specification pages that live on our legacy twiki instance are not available to all users all the time.

Example page:
http://open-services.net/bin/view/Main/QmSpecificationV2

The error goes something like this:

Software error:

Insecure dependency in sysopen while running with -T switch at /usr/local/lib/perl5/site_perl/5.8.8/CGI/Session/Driver/file.pm line 107

Some technical details of the error are available here:

http://twiki.org/cgi-bin/view/Support/SID-02175

There does not seem to be a quick fix, and it is probably not worth investing in fixing this as we are migrating to new infrastructure soon for the site.

Possible Solutions

We need to port this data soon anyway with the new site coming, so here are a few possible solutions. Please contribute to discuss which is the most feasible, or if you see a better solution.

Move the documents to http://www.oasis-oslc.org/. As we are moving all specifications work to OASIS, this is the preferred option.
Move the documents to the new OSLC Mediawiki instance when it is setup
Export the documents to another format and make them available somewhere else on the site. Set up redirects from existing urls. There are some converters out there that can handle twiki format, such as Pandoc.