Giter Site home page Giter Site logo

website's People

Contributors

aguselmaizal avatar areegea avatar bgmarx avatar bottlenecked avatar davydog187 avatar dependabot[bot] avatar desmondmonster avatar ferd avatar gamebox avatar ghislaineguerin avatar janpieper avatar jj1bdx avatar joaquinalcerro avatar johanrhodin avatar josevalim avatar juhalehtonen avatar kianmeng avatar lawrenced avatar marcelfahle avatar marcoow avatar moqa-solutions avatar nurugger07 avatar paulo-ferraz-oliveira avatar pdgonzalez872 avatar pedrosnk avatar peerst avatar rudolfman avatar sstrollo avatar starbelly avatar zacky1972 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

website's Issues

Include footer in all pages

Currently, the footer only shows on the home page. To bring to parity with prod, let's include in the app layout so all pages have it

Add Academic Papers

Would you add the following academic papers:

  %{
    link: "https://ieeexplore.ieee.org/document/7797392",
    name: "Elixir programming language evaluation for IoT (in Japanese)",
    tags: "Elixir",
    date: Date.new(2016, 9, 28)
  },

  %{
    link: "https://zeam-vm.github.io/papers/callback-thread-2nd-WSA.html",
    name: "Plan to Implementation of Lightweight Callback Thread for Elixir and Improvement of Maximum Concurrent Sessions and Latency of Phoenix (in Japanese)",
    tags: "Elixir",
    date: Date.new(2018, 5, 12)
  },

  %{
    link: "https://ipsj.ixsq.nii.ac.jp/ej/index.php?active_action=repository_view_main_item_detail&page_id=13&block_id=8&item_id=190322&item_no=1",
    name: "An Empirical Evaluation to Performance of Elixir for Introducing IoT Systems (in Japanese)",
    tags: "Elixir",
    date: Date.new(2018, 6, 29)
  },

  %{
    link: "https://ipsj.ixsq.nii.ac.jp/ej/index.php?active_action=repository_view_main_item_detail&page_id=13&block_id=8&item_id=190626&item_no=1",
    name: "Implementation of Runtime Environments of C++ and Elixir with the Node Programming Model (in Japanese)",
    tags: "Elixir",
    date: Date.new(2018, 7, 23)
  },

  %{
    link: "https://researchmap.jp/?action=cv_download_main&upload_id=192105",
    name: "A Method Using GPGPU for Super-Parallelization in Elixir Programming (in Japanese)",
    tags: "Elixir",
    date: Date.new(2018, 8, 1)
  },

  %{
    link: "https://ci.nii.ac.jp/naid/170000150470/",
    name: "Hastega: Parallelization of Linear Regression Using SIMD Instruction for Elixir Programming (in Japanese)",
    tags: "Elixir",
    date: Date.new(2018, 1, 17)
  },

  %{
    link: "https://ci.nii.ac.jp/naid/170000180471/",
    name: "SumMag: Design and Implementation of an Analyzer an Extension Mechanism by Meta-programming Using Elixir Macros (in Japanese)",
    tags: "Elixir",
    date: Date.new(2019, 3, 19)
  },

Remove/upgrade vulnerable NPM packages

An audit of the current packages.json yields 4 vulnerable packages:

                       === npm audit security report ===                 
                                                                         
# Run  npm install --save-dev [email protected]  to resolve 2 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Moderate      │ Denial of Service                                            │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ js-yaml                                                      │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ optimize-css-assets-webpack-plugin [dev]                     │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ optimize-css-assets-webpack-plugin > cssnano > postcss-svgo  │
│               │ > svgo > js-yaml                                             │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/788                             │
└───────────────┴──────────────────────────────────────────────────────────────┘


┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High          │ Code Injection                                               │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ js-yaml                                                      │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ optimize-css-assets-webpack-plugin [dev]                     │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ optimize-css-assets-webpack-plugin > cssnano > postcss-svgo  │
│               │ > svgo > js-yaml                                             │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/813                             │
└───────────────┴──────────────────────────────────────────────────────────────┘


# Run  npm install --save-dev [email protected]  to resolve 2 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low           │ Regular Expression Denial of Service                         │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ braces                                                       │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ webpack-cli [dev]                                            │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ webpack-cli > jscodeshift > micromatch > braces              │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/786                             │
└───────────────┴──────────────────────────────────────────────────────────────┘


┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low           │ Regular Expression Denial of Service                         │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ braces                                                       │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ webpack-cli [dev]                                            │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ webpack-cli > webpack-addons > jscodeshift > micromatch >    │
│               │ braces                                                       │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/786                             │
└───────────────┴──────────────────────────────────────────────────────────────┘


found 4 vulnerabilities (2 low, 1 moderate, 1 high) in 14481 scanned packages
  4 vulnerabilities require semver-major dependency updates.

Patch repo importer to load event data into the database

We can migrate the old data with efficacy by patching Erlef.Repo.Importer to load the data into both the existing etso repo and the new data repo. Changeset will have to be transformed in order to comply with the new data event schema.

Inability to login after following welcome link

Hello, I recently signed up to be a member of ERLEF and after sign-up received a link. Upon clicking this link I was returned back to the sign-up page. ie:
image (2)

Upon navigating the site I did not find a component that would allow me to log in. I believe the expected behavior is that I am able to view my profile like the example below.

image (1)

Either way, I think it would be beneficial to have a separate login component that would allow me to view my profile, and do the other things members are allowed to do 😄 with or without the initial link.

Add community page

Similar to erlang.org or elixir-lang.org we should have a community page with useful links to resources and various parts of the communities.

Voting system

The site needs to integrate with the voting system that Benoit suggested.

I still have to look at some different voting system but so far I think heliosvoting could fit our need: https://www.heliosvoting.org
It provides the following features:

  • privacy: ballots are anonymous
  • verifiable: each votes is tracked (you can only vote once for ex)
  • opensource
  • verified
    We are using it in the PSF and it's works verifiable. It is also use by the OSI and many other orgs around the world. We can quickly discuss it but I also think it should be discussed at the board level. Thoughts?
    Benoît

Add tests

We need tests and coverage for erlef and erlef_web namespaces. This should be straight forward and easy to hit 80% if not 100% code coverage.

Events process

This is somewhat related to #57, but I think a little different so I decided to create a new issue for it.

I think we all agree that the more we involve the community the better the results would be for gathering events. Creating an MR for each event does not sound scalable, creating a form that mimics what ElixirForum already does also seems less than optional as well.

I talked to https://elixirforum.com/u/AstonJ (he is the main maintainer for the forum) and he suggested we could use a thread (would be pinned, let's name it EEF Events for now) where all we would need to do is paste links to other threads (eg) in the EEF Events thread.

Here is the events/meetups page: https://elixirforum.com/c/events-confs-meet-ups, we could also the results in json https://elixirforum.com/t/2019-10-25-elixirconfla-medellin-colombia-first-in-latin-america/22365.json

I suggest we look into a way of scraping the EEF Events thread on ElixirForum for events that we post and curate. We could add a couple of rules (filter on posted_by ) and I think we could leverage the data that is already is available to us on ElixirForum.

This would also give folks a way to discuss events and have a platform to engage with other users.

Thoughts?

contact links

It's unclear from the contact page how to subscribe to the mailing-list. Maybe we can add a short description to it or at list links to subscribe/unsubscribe/post.

Also shouldn't we advertise the group chats?

Missing news route for working-groups

Currently on the live site we have posts as "wg" or working-groups. I think perhaps that these posts should be under "eef" (i.e., /news/eef). While I have added the actual post in the repo, it is currently not displayed anywhere.

Clean up PHP references in EEX templates

There are a few straggling PHP references sprinkled around the templates, mostly of the form:

<!-- ?php the_title( '<h1 class="entry-title h2">', '</h1>' ); ? -->

Let's get the definition of this php function and replace the calls with the appropriate eex or static html as appropriate

slack invite endpoint for erlanger.slack.com

The invite link on erlang.org to erlang slack is broken. Specifically, the heroku app that was put in place some time ago and managed by someone who is not around anymore crashes when visited. Slack is not community friendly and does not offer any solid way for managing this out of the box. The best they provide are invite links that do not expire after N seconds, however they do expire after N uses (currently the docs say 2,000).

Since the erlef app exists we can use it to provide a new endpoint for these purposes without concern of a bus factor.

Specification:

  1. Make an end point such as /slack-invite/erlang or something similar
  2. Create a captcha server side that will be rendered on the page for the user to verify against
  3. The user enters an email address, inputs the captcha text and clicks submit
  4. The post is received, the recaptcha verified, and then a slack api call can be made to perform an invite to the email address submitted.
  5. The endpoint will need to be rate limited

After this is implemented and in production we need to contact someone at Ericsson to update the link on erlang.org and likewise for anywhere else that may have a link to the old heroku app.

Reconcile style differences between app and live site.

There are some minor style differences between the app and the live site. As an example, while both use the same font, they appear a little bit different. The differences need to be enumerated here, then broke up into issues. In some cases, we may prefer how something looks or is laid out in the app vs the site.

Integrate calendar

The current events calendar and feed is a wordpress plugin. Ideally we can do an alternative calendar events widget and feed in order to get away from wordpress. This will require some research.

Reference: https://erlef.org/events/

New mailchimp form

The current mailchimp for was made to work with wordpress. We simply need someone with mailchimp access to go in and build a new form not tied to wordpress and update the form in the app.

Admin event approval

In order for submitted events to be displayed on the site, they need to be approved by an admin, thus we need a table (queue) in the admin section for approving submitted events.

Read in page templates to create static page routes

Currently there is a static map defined in the page controller. For the moment, we want to read in the directory listing of lib/erlef_web/templates/page/ on boot to create this map. This requires adjusting the location of all the "pages" in said dir so that the structure reflects the routes in the @static_pages attribute in the page controller.

Simplify calendar event creation using google calendar

Currently adding an event is mostly a manual job, lots of copy/pasta from existing sources which makes for an unpleasant operator experience and error prone. I think we can make use of fullcalendar's gcal support to simplify adding events as well as not having to create blog posts for said events.

The idea would be to add events to a specific google calendar which fullcalendar would pull in. Instead of relying on blog posts for the show route on /events this would have to be completely dynamic and the page would be build using nothing but supplied params and/or hitting google api to get all the information needed to build the page.

It may also be possible to subscribe said google calendar to other calendars to further limit how much work has to be done for events to end up on the site.

The alternative would be to simplify creation of events posts from the command line. This would entail the mix task reaching out to sources such as google calendar to get as much info as possible to limit the amount of manual work done (optimally none) when adding events.

Add Academic Paper: Erlang as an alternative to a non-functional language for communication in a fault-tolerant IoT sensor network

Title:
Erlang as an alternative to a non-functional language for communication in a fault-tolerant IoT sensor network

Details:
By Jimmy Holdö, Department of Computer Science and Engineering, UNIVERSITY OF GOTHENBURG, Gothenburg, Sweden 2019

Link: https://gupea.ub.gu.se/bitstream/2077/63387/1/gupea_2077_63387_1.pdf

I haven't been able to find Jimmy Holdö on Github to ask if we could link this paper (a master's thesis). I'm not sure they would care, but I don't want to assume incorrectly. Thoughts?

Add academic papers page

Hi!

I created a thread on Elixir Forum asking about a list of academic papers involving the Beam[0]. I thought of different ways to make this more visible to the community other than the Elixir Forum. I thought it would be a good idea to not reinvent the wheel and use something that already existed, so I found Papers We Love[1]. I created an issue asking about the convention of adding papers and and being able to filter/tag different papers[2]. It is currently open.

Related to this, I think it would be good to add an Academic Papers section, where we can curate the content we show and organize the content how we want to.

I suggest a simple page where we can link the papers and tag them however we would like. The example I used in the other repo still stands. This would be a link to a paper:

  • Making Reliable Distributed Systems in the Presence of Software Errors | Erlang

I don't want to add short descriptions to the links, as this is yet more work to get the info out there. In my opinion, just links would suffice. We sort alphabetically and call it a day.

Thoughts?

cc: @miriampena

[0] - https://elixirforum.com/t/list-of-academic-research-papers-involving-elixir-erlang/25686/11
[1] - https://github.com/papers-we-love/papers-we-love
[2] - papers-we-love/papers-we-love#581

Add newsletters to site

We need to incorporate our newsletters into site content. Initial thought is to simply have these as generic eef posts.

Implement static blog per working group

We need a static blog per working group using phoenix_markdown to render markdown files. The MVP for this create controller(s), routes, and templates for each blog. In the end, users will be able to send a PR to the repo adding either a markdown file or eex file for a new post.
We also need a blog for our events calendar. See #2 for mail details.

List WG members?

In the Security WG we were wondering what would be the best way to track WG membership. Is this something that could be added to the website?

Update README.md

The README.md does not currently reflect the following:

  • contributing
  • generating events
  • generating news letters

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.