Thanks!

I looked through the notes from back then, some of it is now outdated, not relevant anymore, some of it has been pursued in other places, some plans have turned out completely different along the way.

How do we deal with all the content, for example on pages like this?

actual page structure and content

The URL structure is quite good!

In T662#10289, @sebastian wrote:

two websites: apertus.org for the community side, axiom-camera.com for the commercial side

In T662#10286, @davidak wrote:

The apertus°-Project has 2 sides:

• Products someone can buy (in online Shop) or maybe later rant from companies in our Ecosystem
• a community effort to create an open video capturing plattform (open hardware camera, free software firmware, ...)
  
  The website should reflect that.

Main Menu

The apertus°-Project has 2 sides:

Here are the promised website access stats for the last month:

Maybe a bar graph is better for fast overview of current state. Like that but the bars change their length according to state: http://www.slideteam.net/media/catalog/product/cache/2/thumbnail/543x403/0e7a751fc24f39b632cb88e6c5925d9b/s/e/sequential_timeline_with_gear_bar_graph_and_social_icon_flat_powerpoint_design_Slide01.jpg

@nils are you making progress on the design? can i see the current state?

I haven't forgotten this, but i really had no time.

I really like Markdown for writing, so i was really happy to find https://hackmd.io/

had made some time ago a test setup and i didn't release it. :-/

perfect! thanks

Yep, all appears to be working now.

It was an actual SSL cert issue that should be fixed by now.

Since this task was half implemented in the history page leaving a draft out in the open I reverted the page back to the original state.
Sophie please copy this page and make the changes there.

And I like this picture: https://www.apertus.org/sites/default/files/alpha-prototype-5d_0.jpg maybe you find a space for it.

I don't think we need the alpha subsites menu anymore above the big image.
Please also review the very last paragraphs, there are some missing spaces and the text paragraph style has gone haywire (compare to: https://www.apertus.org/node/166/revisions/3245/view).

I rearranged it and also corrected the text - same with the Alpha text, it's not simple copy/paste. Thought putting it after ars - since the price money funded its development and before the end - which is what's still happening would be a good idea... but could change all of that if you think that's a better idea. Also I thought it's good to put the Alpha in the history, because it is an essential part of the history...

I think its a good idea to change the order to go from beginning (top) to end (bottom).

Hope that's how you envisioned it!

added footer

done:

• remove "AXIOM Alpha" (it can still be found in "List of apertus° Projects")
• move "AXIOM Gamma" to Develop -> Hardware

A few days ago on IRC I said that I'd had second thoughts about clogging up the LP with logos, and that one line of main project partners and another for 'as featured in' might be more appropriate.

what ever floats the boats...

one word: INNOVATION

just as a core question whats the main reason for all the involved people for a open source project like apertus?

Being an internet phenomenon is as you are probably aware by no means assuring quality. I guess there has got to be something out there , which is probably less "fun" but better suited. Probably some talk of Jonathan Zittrain? I can look into it if you think that's necessary...

Dave Jones is an iconic figure.
You might not know him, and he is certainly not always right, but he is one of those internet phenomenons.
If we can find something better on the topic, it would be very welcome, if not, it is probably a lot better than nothing.

if i sent you a six pack of beer im sure you have some hidden a hyper drunken mode where you can redesign it in kicad in just a day. ;-)

Currently we have Eagle design files (switching to KiCAD is still on the roadmap), so we need to have some kind of auto conversion for now if we want to utilize KiCAD for the 3D export.

OK, after watching both of the videos, I'd say they are very easy to understand and not too specific at all. However, the way this dudes presents it is a) quite goofy, which is not only a bad thing as it makes it "fun" to watch and his dumbed down version makes it very easy to understand. Nevertheless, it's a question of style if apertus° necessarily wants to walk this path to the same extend he does (which is kind of implied by embedding the video). b) In the second video he is very focused on the open hardware = good karma part. I think this is a very obvious and therefore boring point to make. Pretty much every other advantage of open hardware is more exciting and interesting than that and he hardly addresses it (maybe besides that you can still get rich and famous with open hardware products, which is again not the greatest point to make) – but that's my personal opinion.
Generally, you can tell that it is very community orientated and maybe that's what apertus° is aiming for - my question is: isn't that where apertus° has already scored big time and wouldn't it be time to convince these from outside of the community of it's awesomeness?

You might have to zoom in to read the text on the attached image.

But this tactic would do three things at the same time. It would generate some funding, give sponsors something back, and it also encourages other firms to contribute alongside counterparts.

If you're anything like me then you're probably not overly keen on commercialisation. Advertising can be pretty vulgar let's face it. In fact, I'd go so far as to say that I'm averse to advertising. However, and from what I've picked up so far, funding for development is sorely needed. At this stage some advertising is probably a good strategy.

not yet

Did you already download the free Skin?

suggest using namespaces ( some lines in configuration file ), Lockdown extension if restricted access is needed ( don't know/cannot decide if needed), NSFileRepo extension if restricted access should be applicable for documents also ...

is this task still relevant?

Is this still the case?
please test and close task otherwise

I think that information is best obtained from the datasheets directly, no?

please do, the guy is a legend :)

Wow - I find it really difficult to listen to this Aussie troll, couldn't make it past the intro yet - will try to pull through to form a proper opinion...

forum is closed already

all added: https://www.apertus.org/axiom-beta-roadmap

Triple DisplayPort Link Module added

3x PMOD added

1xHDMI modul (finished) added

also new: triple PMOD modul (finished)
1xHDMI modul (finished)

In T133#9002, @christophvarga wrote:

mine:
-push autofocus
-push autoiris
-(zoom in/out)

One thing we have to think of Ehen choosing faders is that the physical Position can be different from the actual Software value when we allow Software control as well. Just to be aware.. I like the idea if faders, the actual remote concept put those extra features on extensions. You See it can n this (old) concept here:

great, suggest a more detailed Description, e.g. zoom in/out is accomplished by two buttons, or some device where the zoom speed also can be controlled for soft start and end of zoom.

I want to start a list of your most used controls while recording sorted by priority. this rank can help us programming our first remote.

Current progress: https://www.apertus.org/node/404