Next Page: 10000

          Re: Best country to pick at mens bathing naked (river/beach)      Cache   Translate Page      
You don´t need to google anything, just go there. A good spot is the Rokel river in Magburaka, a town in northern Sierra Leone or the Wanje river in Pujehun, in the south of the same country. Any river or even small brook in this country has people bathing in it and you can enjoy to see these amazing guys just naked there. It is really a plus if you just join them....
          Re: Sex tourism in Gambia...      Cache   Translate Page      
From www gvnet.com I transfer the fllowing passage.

Human Trafficking and Modern-day Slavery

The Gambia is a source, transit, and destination country for children and women trafficked for the purposes of forced labor and commercial sexual exploitation. Within The Gambia, women and girls, and to a lesser extent boys, are trafficked for sexual exploitation, in particular to meet the demand for European sex tourism, and for domestic servitude. Boys are trafficked within the country for forced begging by religious teachers and for street vending. Transnationally, women, girls and boys from neighboring countries are trafficked to The Gambia for the same purposes listed above. Primary source countries are Senegal, Mali, Sierra Leone, Liberia, Ghana, Nigeria, Guinea-Bissau, Guinea and Benin. Trafficking of Gambian boys to Senegal for forced begging and Senegalese boys to The Gambia for the same purpose is particularly prevalent. Gambian women and girls are trafficked to Senegal for domestic servitude, and possibly for sexual exploitation. Gambian women and children may be trafficked to Europe through trafficking schemes disguised as migrant smuggling. Reports in the last two years of Gambian, Senegalese, and nationals of other neighboring countries being transported from The Gambia to Spain by boat appear to be predominantly cases of smuggling rather than trafficking. - U.S. State Dept Trafficking in Persons Report, June, 2008 [
          World: Global Weather Hazards Summary: September 14 - 20, 2018      Cache   Translate Page      
Source: Famine Early Warning System Network
Country: Afghanistan, Benin, Burkina Faso, Costa Rica, Côte d'Ivoire, Democratic Republic of the Congo, Dominican Republic, El Salvador, Eritrea, Ethiopia, Gambia, Ghana, Guatemala, Guinea, Guinea-Bissau, Haiti, Honduras, Kazakhstan, Kyrgyzstan, Liberia, Mali, Mauritania, Nicaragua, Niger, Nigeria, Panama, Senegal, Sierra Leone, Somalia, South Sudan, Sudan, Tajikistan, Togo, Uganda, World, Yemen

Flood risk remains high over parts of Nigeria, as heavy rainfall is expected to continue

Africa Weather Hazards

  1. Heavy rainfall caused flooding in western and southern Nigeria. The forecast rain during the next week increases the risks for flooding over the region.

  2. Torrential rain has increased the level of the Atbara and Dindir Rivers. Additional rainfall over the region is likely to further raise water levels, including the Nile River and its tributaries.

  3. Irregular rainfall since June has resulted in deteriorated ground conditions across parts of western Uganda, northeastern DRC, and southern South Sudan.

  4. Despite an overall improvement in rainfall over the past four weeks, deficits remain over portions of southwestern Ethiopia and eastern South Sudan.


          Bukan di Indonesia, Penyakit Cacar Monyet Umum Ditemukan di Negara Ini      Cache   Translate Page      

Liputan6.com, Jakarta Penyakit cacar monyet yang biasanya ditemukan di negara-negara Afrika kini terdeteksi di Inggris. Kasus cacar monyet di Inggris tercatat telah menginfeksi dua orang dalam empat hari terakhir, hal itu telah dikonfirmasi oleh Badan Kesehatan Masyarakat Inggris.

Penyakit menular ini pertama kali terdiagnosis pada warga negara Nigeria yang tinggal di Cornwall pada Sabtu, 8 September 2018. Orang tersebut kemudian dilarikan ke London. Lalu, Selasa, 11 September 2018, pasien cacar monyet kedua ditemukan di Blackpool. Pasien itu baru saja berkunjung ke Nigeria dan kini dirawat di sebuah rumah sakit di Liverpool, mengutip laman Express, Kamis (13/9/2018).

Penyakit cacar monyet pernah melanda enam negara di Afrika pada 2017. Keenam negara tersebut yakni Afrika Tengah, Republik Demokrat Congo, Liberia, Nigeria, Sierra Leone, serta Republik Congo. Data Organisasi Kesehatan Dunia (WHO) menyebut, Nigeria mengalami outbreak cacar monyet paling besar pada tahun tersebut. Tercatat ada 197 suspek dan 68 orang benar terdiagnosis cacar monyet.

Tak hanya menginfeksi manusia, cacar monyet juga ditemukan pada hewan liar di Kamerun, Pantai Gading, serta Republik Demokrat Congo.

Sementara, penyakit cacar monyet pada manusia seringkali dilaporkan berasal dari lingkungan hutan belantara yang penduduknya mengandalkan daging hewan semak sebagi sumber protein.

"Proses berburu serta persiapan daging hewan semak menjadi faktor risiko infeksi cacar monyet," ungkap WHO.

 


          The price of precarious labour in contemporary warfare      Cache   Translate Page      

One year previously, a British private security company providing services for the US government reached an agreement with the Sierra Leonean government to employ up to 10,000 Sierra Leonean ex-servicemen for security contracting in Iraq.

The post The price of precarious labour in contemporary warfare appeared first on OUPblog.


          Sierra Leone:Food Security and Nutrition Report 2018821 Million People Now Hungry, Over 150 Million Children Stunted      Cache   Translate Page      
[Concord] By Alusine Sesay (Source: AllAfrica News: Health and Medicine)
          Knapp 40.000 Klicks: Würzburg-Song von Flüchtling Aliyas polarisiert      Cache   Translate Page      
Der 18-Jährige singt über seine Würzburg Liebe. Foto: Screenshot Youtube VideoMit über 38.000 Klicks (Stand 13 .September 2018) innerhalb von drei Wochen, scheint der Sänger und Rapper Aliyas schon zu einer gewisse Bekanntheit mit seinem Song „Würzburg“ geworden zu sein. Doch nicht nur Positives lässt sich in den Kommentaren unter seinem YouTube Video finden. Ali erzählt uns, dass er ursprünglich aus Sierra Leones Hauptstadt Freetown…
          The price of precarious labour in contemporary warfare      Cache   Translate Page      

One year previously, a British private security company providing services for the US government reached an agreement with the Sierra Leonean government to employ up to 10,000 Sierra Leonean ex-servicemen for security contracting in Iraq.

The post The price of precarious labour in contemporary warfare appeared first on OUPblog.


          African countries urged to toughen laws on female genital mutilation      Cache   Translate Page      
LONDON, Sept 13 (Thomson Reuters Foundation) – Millions of girls in Africa are at risk of female genital mutilation because their governments are failing to enforce laws banning the internationally condemned practice, campaigners said on Thursday. Six countries which are home to 16 million girls – Chad, Liberia, Mali, Sierra Leone, Somalia and Sudan – […]
          Africa:African Artists Wow Another Continent Down Under      Cache   Translate Page      
[The Conversation Africa] In recent years, increasing numbers of people have moved from all parts of Africa to Australia. The largest numbers have come from South Africa, Sudan, South Sudan, Zimbabwe, Egypt, Ethiopia, Kenya, Somalia and Sierra Leone.
          Africa:African Artists Wow Another Continent Down Under      Cache   Translate Page      
[The Conversation Africa] In recent years, increasing numbers of people have moved from all parts of Africa to Australia. The largest numbers have come from South Africa, Sudan, South Sudan, Zimbabwe, Egypt, Ethiopia, Kenya, Somalia and Sierra Leone. Reported by allAfrica.com 45 minutes ago.
          The price of precarious labour in contemporary warfare      Cache   Translate Page      

One year previously, a British private security company providing services for the US government reached an agreement with the Sierra Leonean government to employ up to 10,000 Sierra Leonean ex-servicemen for security contracting in Iraq.

The post The price of precarious labour in contemporary warfare appeared first on OUPblog.


          Drupal blog: Who sponsors Drupal development? (2017-2018 edition)      Cache   Translate Page      

This blog has been re-posted and edited with permission from Dries Buytaert's blog. Please leave your comments on the original post.

For the past two years, I've examined Drupal.org's commit data to understand who develops Drupal, how much of that work is sponsored, and where that sponsorship comes from.

I have now reported on this data for three years in a row, which means I can start to better compare year-over-year data. Understanding how an open-source project works is important because it establishes a benchmark for project health and scalability.

I would also recommend taking a look at the 2016 report or the 2017 report. Each report looks at data collected in the 12-month period between July 1st and June 30th.

This year's report affirms that Drupal has a large and diverse community of contributors. In the 12-month period between July 1, 2017 and June 30, 2018, 7,287 different individuals and 1,002 different organizations contributed code to Drupal.org. This include contributions to Drupal core and all contributed projects on Drupal.org.

In comparison to last year's report, both the number of contributors and contributions has increased. Our community of contributors (including both individuals and organizations) is also becoming more diverse. This is an important area of growth, but there is still work to do.

For this report, we looked at all of the issues marked "closed" or "fixed" in our ticketing system in the 12-month period from July 1, 2017 to June 30, 2018. This includes Drupal core and all of the contributed projects on Drupal.org, across all major versions of Drupal. This year, 24,447 issues were marked "closed" or "fixed", a 5% increase from the 23,238 issues in the 2016-2017 period. This averages out to 67 feature improvements or bug fixes a day.

In total, we captured 49,793 issue credits across all 24,447 issues. This marks a 17% increase from the 42,449 issue credits recorded in the previous year. Of the 49,793 issue credits reported this year, 18% (8,822 credits) were for Drupal core, while 82% (40,971 credits) went to contributed projects.

"Closed" or "fixed" issues are often the result of multiple people working on the issue. We try to capture who contributes through Drupal.org's unique credit system. We used the data from the credit system for this analysis. There are a few limitations with this approach, which we'll address at the end of this report.

What is the Drupal.org credit system?

In the spring of 2015, after proposing ideas for giving credit and discussing various approaches at length, Drupal.org added the ability for people to attribute their work to an organization or customer in the Drupal.org issue queues. Maintainers of Drupal modules, themes, and distributions can award issue credits to people who help resolve issues with code, translations, documentation, design and more.

Example issue credit on drupal org

A screenshot of an issue comment on Drupal.org. You can see that jamadar worked on this patch as a volunteer, but also as part of his day job working for TATA Consultancy Services on behalf of their customer, Pfizer.

Credits are a powerful motivator for both individuals and organizations. Accumulating credits provides individuals with a way to showcase their expertise. Organizations can utilize credits to help recruit developers, to increase their visibility within the Drupal.org marketplace, or to showcase their Drupal expertise.

Who is working on Drupal?

In the 12-month period between July 1, 2017 to June 30, 2018, 24,447, Drupal.org received code contributions from 7,287 different individuals and 1,002 different organizations.

Contributions by individuals vs organizations

While the number of individual contributors rose, a relatively small number of individuals still do the majority of the work. Approximately 48% of individual contributors received just one credit. Meanwhile, the top 30 contributors (the top 0.4%) account for more than 24% of the total credits. These individuals put an incredible amount of time and effort in developing Drupal and its contributed projects:

Rank Username Issues
1 RenatoG 851
2 RajabNatshah 745
3 jrockowitz 700
4 adriancid 529
5 bojanz 515
6 Berdir 432
7 alexpott 414
8 mglaman 414
9 Wim Leers 395
10 larowlan 360
11 DamienMcKenna 353
12 dawehner 340
13 catch 339
14 heddn 327
15 xjm 303
16 pifagor 284
17 quietone 261
18 borisson_ 255
19 adci_contributor 255
20 volkswagenchick 254
21 drunken monkey 231
22 amateescu 225
23 joachim 199
24 mkalkbrenner 195
25 chr.fritsch 185
26 gaurav.kapoor 178
27 phenaproxima 177
28 mikeytown2 173
29 joelpittet 170
30 timmillwood 169

Out of the top 30 contributors featured, 15 were also recognized as top contributors in our 2017 report. These Drupalists' dedication and continued contribution to the project has been crucial to Drupal's development. It's also exciting to see 15 new names on the list. This mobility is a testament to the community's evolution and growth. It's also important to recognize that a majority of the 15 repeat top contributors are at least partially sponsored by an organization. We value the organizations that sponsor these remarkable individuals, because without their support, it could be more challenging to be in the top 30 year over year.

How diverse is Drupal?

Next, we looked at both the gender and geographic diversity of Drupal.org code contributors. While these are only two examples of diversity, this is the only available data that contributors can currently choose to share on their Drupal.org profiles. The reported data shows that only 7% of the recorded contributions were made by contributors that do not identify as male, which continues to indicates a steep gender gap. This is a one percent increase compared to last year. The gender imbalance in Drupal is profound and underscores the need to continue fostering diversity and inclusion in our community.

To address this gender gap, in addition to advancing representation across various demographics, the Drupal community is supporting two important initiatives. The first is to adopt more inclusive user demographic forms on Drupal.org. Adopting Open Demographics on Drupal.org will also allow us to improve reporting on diversity and inclusion, which in turn will help us better support initiatives that advance diversity and inclusion. The second initiative is supporting the Drupal Diversity and Inclusion Contribution Team, which works to better include underrepresented groups to increase code and community contributions. The DDI Contribution Team recruits team members from diverse backgrounds and underrepresented groups, and provides support and mentorship to help them contribute to Drupal.

It's important to reiterate that supporting diversity and inclusion within Drupal is essential to the health and success of the project. The people who work on Drupal should reflect the diversity of people who use and work with the software. While there is still a lot of work to do, I'm excited about the impact these various initiatives will have on future reports.

Contributions by gender

When measuring geographic diversity, we saw individual contributors from 6 different continents and 123 different countries:

Contributions by continent

Contributions by country

The top 20 countries from which contributions originate. The data is compiled by aggregating the countries of all individual contributors behind each commit. Note that the geographical location of contributors doesn't always correspond with the origin of their sponsorship. Wim Leers, for example, works from Belgium, but his funding comes from Acquia, which has the majority of its customers in North America.

123 different countries is seven more compared to the 2017 report. The new countries include Rwanda, Namibia, Senegal, Sierra Leone, and Swaziland, Zambia. Seeing contributions from more African countries is certainly a highlight.

How much of the work is sponsored?

Issue credits can be marked as "volunteer" and "sponsored" simultaneously (shown in jamadar's screenshot near the top of this post). This could be the case when a contributor does the minimum required work to satisfy the customer's need, in addition to using their spare time to add extra functionality.

While Drupal started out as a 100% volunteer-driven project, today the majority of the code on Drupal.org is sponsored by organizations. Only 12% of the commit credits that we examined in 2017-2018 were "purely volunteer" credits (6,007 credits), in stark contrast to the 49% that were "purely sponsored". In other words, there were four times as many "purely sponsored" credits as "purely volunteer" credits.

Contributions by volunteer vs sponsored

A few comparisons between the 2017-2018 and the 2016-2017 data:

  • The credit system is being used more frequently. In total, we captured 49,793 issue credits across all 24,447 issues in the 2017-2018 period. This marks a 17% increase from the 42,449 issue credits recorded in the previous year. Between July 1, 2016 and June 30, 2017, 28% of all credits had no attribution while in the period between July 1, 2017 to June 30, 2018, only 25% of credits lacked attribution. More people have become aware of the credit system, the attribution options, and their benefits.
  • Sponsored credits are growing faster than volunteer credits. Both "purely volunteer" and "purely sponsored" credits grew, but "purely sponsored" credits grew faster. There are two reasons why this could be the case: (1) more contributions are sponsored and (2) organizations are more likely to use the credit system compared to volunteers.

No data is perfect, but it feels safe to conclude that most of the work on Drupal is sponsored. At the same time, the data shows that volunteer contribution remains very important to Drupal. Maybe most importantly, while the number of volunteers and sponsors has grown year over year in absolute terms, sponsored contributions appear to be growing faster than volunteer contributions. This is consistent with how open source projects grow and scale.

Who is sponsoring the work?

Now that we've established a majority of contributions to Drupal are sponsored, we want to study which organizations contribute to Drupal. While 1,002 different organizations contributed to Drupal, approximately 50% of them received four credits or less. The top 30 organizations (roughly the top 3%) account for approximately 48% of the total credits, which implies that the top 30 companies play a crucial role in the health of the Drupal project. The graph below shows the top 30 organizations and the number of credits they received between July 1, 2017 and June 30, 2018:

Top 30 organizations contributing to Drupal

The top 30 contributing organizations based on the number of Drupal.org commit credits.

While not immediately obvious from the graph above, a variety of different types of companies are active in Drupal's ecosystem:

Category Description
Traditional Drupal businesses Small-to-medium-sized professional services companies that primarily make money using Drupal. They typically employ fewer than 100 employees, and because they specialize in Drupal, many of these professional services companies contribute frequently and are a huge part of our community. Examples are Chapter Three and Lullabot (both shown on graph).
Digital marketing agencies Larger full-service agencies that have marketing-led practices using a variety of tools, typically including Drupal, Adobe Experience Manager, Sitecore, WordPress, etc. They tend to be larger, with the larger agencies employing thousands of people. Examples are Wunderman and Mirum.
System integrators Larger companies that specialize in bringing together different technologies into one solution. Example system agencies are Accenture, TATA Consultancy Services, Capgemini and CI&T (shown on graph).
Technology and infrastructure companies Examples are Acquia (shown on graph), Lingotek, BlackMesh, Rackspace, Pantheon and Platform.sh.
End-users Examples are Pfizer (shown on graph) or NBCUniversal.

A few observations:

  • Almost all of the sponsors in the top 30 are traditional Drupal businesses. Companies like MD Systems (12 employees), Valuebound (58 employees), Chapter Three (33 employees), Commerce Guys (13 employees) and PreviousNext (22 employees) are, despite their size, critical to Drupal's success.
  • Compared to these traditional Drupal businesses, Acquia has nearly 800 employees and at least ten full-time Drupal contributors. Acquia works to resolve some of the most complex issues on Drupal.org, many of which are not recognized by the credit system (e.g. release management, communication, sprint organizing, and project coordination). Acquia added several full-time contributors compared to last year, however, I believe that Acquia should contribute even more due to its comparative size.
  • No digital marketing agencies show up in the top 30, though some of them are starting to contribute. It's exciting that an increasing number of digital marketing agencies are delivering beautiful experiences using Drupal. As a community, we need to work to ensure that each of these firms are contributing back to the project with the same commitment that we see from firms like Commerce Guys, CI&T or Acro Media. Compared to last year, we have not made meaningful progress on growing contributions from digital marketing agencies. It would be interesting to see what would happen if more large organizations mandated contributions from their partners. Pfizer, for example, only works with agencies and vendors that contribute back to Drupal, and requires that its agency partners contribute to open source. If more organizations took this stance, it could have a big impact on the number of digital agencies that contribute to Drupal
  • The only system integrator in the top 30 is CI&T, which ranked 3rd with 959 credits. As far as system integrators are concerned, CI&T is a smaller player with approximately 2,500 employees. However, we do see various system integrators outside of the top 30, including Globant, Capgemini, Sapient and TATA Consultancy Services. Each of these system integrators reported 30 to 85 credits in the past year. The top contributor is TATA with 85 credits.
  • Infrastructure and software companies also play an important role in our community, yet only Acquia appears in the top 30. While Acquia has a professional services division, more than 75% of the contributions come from the product organization. Other infrastructure companies include Pantheon and Platform.sh, which are both venture-backed, platform-as-a-service companies that were born from the Drupal community. Pantheon has 6 credits and Platform.sh has 47 credits. Amazee Labs, a company that is building an infrastructure business, reported 40 credits. Compared to last year, Acquia and Rackspace have slightly more credits, while Pantheon, Platform.sh and Amazee contributed less. Lingotek, a vendor that offers cloud-based translation management software has 84 credits.
  • We also saw three end-users in the top 30 as corporate sponsors: Pfizer (491 credits, up from 251 credits the year before), Thunder (432 credits), and the German company, bio.logis (319 credits, up from 212 credits the year before). Other notable customers outside of the top 30, include Workday, Wolters Kluwer, Burda Media, YMCA and OpenY, CARD.com and NBCUniversal. We also saw contributions from many universities, including University of Colorado Boulder, University of Waterloo, Princeton University, University of Adelaide, University of Sydney, University of Edinburgh, McGill University and more.

Contributions by technology companies

We can conclude that technology and infrastructure companies, digital marketing agencies, system integrators and end-users are not making significant code contributions to Drupal.org today. How can we explain this disparity in comparison to the traditional Drupal businesses that contribute the most? We believe the biggest reasons are:

  1. Drupal's strategic importance. A variety of the traditional Drupal agencies almost entirely depend on Drupal to support their businesses. Given both their expertise and dependence on Drupal, they are most likely to look after Drupal's development and well-being. Contrast this with most of the digital marketing agencies and system integrators who work with a diversified portfolio of content management platforms. Their well-being is less dependent on Drupal's success.
  2. The level of experience with Drupal and open source. Drupal aside, many organizations have little or no experience with open source, so it is important that we motivate and teach them to contribute.
  3. Legal reservations. We recognize that some organizations are not legally permitted to contribute, let alone attribute their customers. We hope that will change as open source continues to get adopted.
  4. Tools barriers. Drupal contribution still involves a patch-based workflow on Drupal.org's unique issue queue system. This presents a fairly steep learning curve to most developers, who primarily work with more modern and common tools such as GitHub. We hope to lower some of these barriers through our collaboration with GitLab.
  5. Process barriers. Getting code changes accepted into a Drupal project — especially Drupal core — is hard work. Peer reviews, gates such as automated testing and documentation, required sign-offs from maintainers and committers, knowledge of best practices and other community norms are a few of the challenges a contributor must face to get code accepted into Drupal. Collaborating with thousands of people on a project as large and widely-used as Drupal requires such processes, but new contributors often don't know that these processes exist, or don't understand why they exist.

We should do more to entice contribution

Drupal is used by more than one million websites. Everyone who uses Drupal benefits from work that thousands of other individuals and organizations have contributed. Drupal is great because it is continuously improved by a diverse community of contributors who are enthusiastic to give back.

However, the vast majority of the individuals and organizations behind these Drupal websites never participate in the development of the project. They might use the software as it is or don't feel the need to help drive its development. We have to provide more incentive for these individuals and organizations to contribute back to the project.

Consequently, this data shows that the Drupal community can do more to entice companies to contribute code to Drupal.org. The Drupal community has a long tradition of encouraging organizations to share code rather than keep it behind firewalls. While the spirit of the Drupal project cannot be reduced to any single ideology — not every organization can or will share their code — we would like to see organizations continue to prioritize collaboration over individual ownership.

We understand and respect that some can give more than others and that some might not be able to give back at all. Our goal is not to foster an environment that demands what and how others should give back. Our aim is not to criticize those who do not contribute, but rather to help foster an environment worthy of contribution. This is clearly laid out in Drupal's Values and Principles.

Given the vast amount of Drupal users, we believe continuing to encourage organizations and end-users to contribute is still a big opportunity. From my own conversations, it's clear that organizations still need need education, training and help. They ask questions like: "Where can we contribute?", "How can we convince our legal department?", and more.

There are substantial benefits and business drivers for organizations that contribute: (1) it improves their ability to sell and win deals and (2) it improves their ability to hire. Companies that contribute to Drupal tend to promote their contributions in RFPs and sales pitches. Contributing to Drupal also results in being recognized as a great place to work for Drupal experts.

What projects have sponsors?

To understand where the organizations sponsoring Drupal put their money, I've listed the top 20 most sponsored projects:

Rank Project name Issues
1 Drupal core 5919
2 Webform 905
3 Drupal Commerce 607
4 Varbase: The Ultimate Drupal 8 CMS Starter Kit (Bootstrap Ready) 551
5 Commerce Point of Sale (POS) 324
6 Views 318
7 Commerce Migrate 307
8 JSON API 304
9 Paragraphs 272
10 Open Social 222
11 Search API Solr Search 212
12 Drupal Connector for Janrain Identity Cloud 197
13 Drupal.org security advisory coverage applications 189
14 Facets 171
15 Open Y 162
16 Metatag 162
17 Web Page Archive 154
18 Drupal core - JavaScript Modernization Initiative 145
19 Thunder 144
20 XML sitemap 120

Who is sponsoring the top 30 contributors?

Rank Username Issues Volunteer Sponsored Not specified Sponsors
1 RenatoG 851 0% 100% 0% CI&T (850), Johnson & Johnson (23)
2 RajabNatshah 745 14% 100% 0% Vardot (653), Webship (90)
3 jrockowitz 700 94% 97% 1% The Big Blue House (680), Memorial Sloan Kettering Cancer Center (7), Rosewood Marketing (2), Kennesaw State University (1)
4 adriancid 529 99% 19% 0% Ville de Montréal (98)
5 bojanz 515 0% 98% 2% Commerce Guys (503), Torchbox (17), Adapt (6), Acro Media (4), Bluespark (1)
6 Berdir 432 0% 92% 8% MD Systems (396), Translations.com (10), Acquia (2)
7 alexpott 414 13% 84% 10% Chapter Three (123), Thunder (120), Acro Media (103)
8 mglaman 414 5% 96% 1% Commerce Guys (393), Impactiv (17), Circle Web Foundry (16), Rosewood Marketing (14), LivePerson (13), Bluespark (4), Acro Media (4), Gaggle.net (3), Thinkbean (2), Matsmart (2)
9 Wim Leers 395 8% 94% 0% Acquia (371)
10 larowlan 360 13% 97% 1% PreviousNext (350), University of Technology, Sydney (24), Charles Darwin University (10), Australian Competition and Consumer Commission (ACCC) (1), Department of Justice & Regulation, Victoria (1)
11 DamienMcKenna 353 1% 95% 5% Mediacurrent (334)
12 dawehner 340 48% 86% 4% Chapter Three (279), Torchbox (10), Drupal Association (5), Tag1 Consulting (3), Acquia (2), TES Global (1)
13 catch 339 1% 97% 3% Third and Grove (320), Tag1 Consulting (8)
14 heddn 327 2% 99% 1% MTech (325)
15 xjm 303 0% 97% 3% Acquia (293)
16 pifagor 284 32% 99% 1% GOLEMS GABB (423), Drupal Ukraine Community (73)
17 quietone 261 48% 55% 5% Acro Media (143)
18 borisson_ 255 93% 55% 3% Dazzle (136), Intracto digital agency (1), Acquia (1), DUG BE vzw (Drupal User Group Belgium) (1)
19 adci_contributor 255 0% 100% 0% ADCI Solutions (255)
20 volkswagenchick 254 1% 100% 0% Hook 42 (253)
21 drunken monkey 231 91% 22% 0% DBC (24), Vizala (20), Sunlime Web Innovations GmbH (4), Wunder Group (1), epiqo (1), Zebralog (1)
22 amateescu 225 3% 95% 3% Pfizer (211), Drupal Association (1), Chapter Three (1)
23 joachim 199 56% 44% 19% Torchbox (88)
24 mkalkbrenner 195 0% 99% 1% bio.logis (193), OSCE: Organization for Security and Co-operation in Europe (119)
25 chr.fritsch 185 0% 99% 1% Thunder (183)
26 gaurav.kapoor 178 0% 81% 19% OpenSense Labs (144), DrupalFit (55)
27 phenaproxima 177 0% 99% 1% Acquia (176)
28 mikeytown2 173 0% 0% 100%
29 joelpittet 170 28% 74% 16% The University of British Columbia (125)
30 timmillwood 169 1% 100% 0% Pfizer (169), Appnovation (163), Millwood Online (6)

We observe that the top 30 contributors are sponsored by 58 organizations. This kind of diversity is aligned with our desire to make sure that Drupal is not controlled by a single organization. These top contributors and organizations are from many different parts of the world, and work with customers large and small. Nonetheless, we will continue to benefit from an increased distribution of contribution.

Limitations of the credit system and the data

While the benefits are evident, it is important to note a few of the limitations in Drupal.org's current credit system:

  • Contributing to issues on Drupal.org is not the only way to contribute. Other activities, such as sponsoring events, promoting Drupal, and providing help and mentorship are also important to the long-term health of the Drupal project. Many of these activities are not currently captured by the credit system. For this post, we chose to only look at code contributions.
  • We acknowledge that parts of Drupal are developed on GitHub and therefore aren't fully credited on Drupal.org. The actual number of contributions and contributors could be significantly higher than what we report. The Drupal Association is working to integrate GitLab with Drupal.org. GitLab will provide support for "merge requests", which means contributing to Drupal will feel more familiar to the broader audience of open source contributors who learned their skills in the post-patch era. Some of GitLab's tools, such as inline editing and web-based code review, will also lower the barrier to contribution, and should help us grow both the number of contributions and contributors on Drupal.org.
  • Even when development is done on Drupal.org, the credit system is not used consistently. As using the credit system is optional, a lot of code committed on Drupal.org has no or incomplete contribution credits.
  • Not all code credits are the same. We currently don't have a way to account for the complexity and quality of contributions; one person might have worked several weeks for just one credit, while another person might receive a credit for ten minutes of work. In the future, we should consider issuing credit data in conjunction with issue priority, patch size, etc. This could help incentivize people to work on larger and more important problems and save coding standards improvements for new contributor sprints. Implementing a scoring system that ranks the complexity of an issue would also allow us to develop more accurate reports of contributed work.

Like Drupal itself, the Drupal.org credit system needs to continue to evolve. Ultimately, the credit system will only be useful when the community uses it, understands its shortcomings, and suggests constructive improvements.

Conclusion

Our data confirms that Drupal is a vibrant community full of contributors who are constantly evolving and improving the software. While we have amazing geographic diversity, we still need greater gender diversity, in addition to better representation across various demographic groups. Our analysis of the Drupal.org credit data concludes that most contributions to Drupal are sponsored. At the same time, the data shows that volunteer contribution remains very important to Drupal.

As a community, we need to understand that a healthy open source ecosystem includes more than the traditional Drupal businesses that contribute the most. We still don't see a lot of contribution from the larger digital marketing agencies, system integrators, technology companies, or end-users of Drupal — we believe that might come as these organizations build out their Drupal practices and Drupal becomes more strategic for them.

To grow and sustain Drupal, we should support those that contribute to Drupal and find ways to get those that are not contributing involved in our community. We invite you to help us continue to strengthen our ecosystem.


          The Morning Sound Alternative 09-13-2018 with Dennis Rider      Cache   Translate Page      
Playlist:

Casuarina- Dora - No Passo De Caymmi
Oneohtrix Point Never- Still Stuff That Doesnt Happen - Age Of
Kiran Ahluwalia- Taskeen - Sanata Stillness
Kurt Elling- Tutti For Cootie - 1619 Broadway The Brill Building Project
Ron Jackson Xavier Davis Lisa Kirchner Vincente Archer Sherman Irby Willie Jones III- Night Make My Day - Something To Sing About
Chris Dave And The Drumhedz- Job Well Done feat Anna Wise SiR - Chris Dave And The Drumhedz
RRNOW- Change Of Tone - Collagically Speaking feat Robert Glasper Terrace Martin Christian Scott ATunde Adjuah Derrick Hodge Taylor McFerrin Justin Tyson
Mokoomba- Mvula - Rising Tide
Kat Edmonson- The Best - The Big Picture
Ayrad- Sidi Hbibi - Ayrad
Pine Leaf Boys- La Vie Est Courte - Danser
The Jones Family Singers- You Woke Me Up This Morning - The Spirit Speaks
Aurelio- Nari Golu - Lndini
Tuba Skinny- BloodThirsty Blues - Pyramid Strut
Alsarah The Nubatones- Fugu Shams Alhurria - Silt
Alex Clare- Three Hearts - Three Hearts
Breabach- The Poetic Milkman - Urlar
Andria Simone- Im In Trouble - Good Lovin
Sierra Leones Refugee All Stars- Ghana Baby - Libation
Pomplamoose- Video Killed The Radio Star - Season 2
HSao- On Nestpas Daccord - Oria
Alice Russell- For A While - To Dust
Sharon Jones The DapKings- Now I See - Give The People What They Want
JC Brooks The Uptown Sound- Rouse Yourself - Howl
DeJ Loaf Leon Bridges- Liberated - Liberated Single
Karen Wolfe- I Got A Good Man - Telling It Like It Is
Mel Waiters- Best Love Making - Poor Side Of Town
Joe Driscoll Sekou Kouyate- Wonamati - Faya
Radio Radio- Holiday - Ej Feel Zoo


playlist URL: http://www.afterfm.com/index.cfm/fuseaction/playlist.listing/showInstanceID/49/playlistDate/2018-09-13
          Citizens lead Sierra Leone’s path to quality service delivery      Cache   Translate Page      
Community of Mapaki's Community Monitoring Group Members, Ward 112, Bombali District. Photo: World Bank

When was the last time you participated in a community and worked together to reach a common goal? Communities across Sierra Leone are doing just that.


          Investor Seeks to Create Jobs in Sierra Leone      Cache   Translate Page      
[Concord] ... investment in housing, navigation satellite, gold refinery underway
          UK Answers Bio's Call, Sends 8 Sierra Leonean Students to Study      Cache   Translate Page      
[Concord] Minister of Further Education and Research Professor Aiah Gbakima, British High Commissioner Guy Warrington, Head of DFID Sierra Leone Mary Hunt, Head of British Council Tony Reilly and the eight successful candidates
          Ambassador Ndomahina to Unify Sierra Leonean Community in China      Cache   Translate Page      
[Concord] By Joseph S. Margai in Beijing


Next Page: 10000

Site Map 2018_01_14
Site Map 2018_01_15
Site Map 2018_01_16
Site Map 2018_01_17
Site Map 2018_01_18
Site Map 2018_01_19
Site Map 2018_01_20
Site Map 2018_01_21
Site Map 2018_01_22
Site Map 2018_01_23
Site Map 2018_01_24
Site Map 2018_01_25
Site Map 2018_01_26
Site Map 2018_01_27
Site Map 2018_01_28
Site Map 2018_01_29
Site Map 2018_01_30
Site Map 2018_01_31
Site Map 2018_02_01
Site Map 2018_02_02
Site Map 2018_02_03
Site Map 2018_02_04
Site Map 2018_02_05
Site Map 2018_02_06
Site Map 2018_02_07
Site Map 2018_02_08
Site Map 2018_02_09
Site Map 2018_02_10
Site Map 2018_02_11
Site Map 2018_02_12
Site Map 2018_02_13
Site Map 2018_02_14
Site Map 2018_02_15
Site Map 2018_02_15
Site Map 2018_02_16
Site Map 2018_02_17
Site Map 2018_02_18
Site Map 2018_02_19
Site Map 2018_02_20
Site Map 2018_02_21
Site Map 2018_02_22
Site Map 2018_02_23
Site Map 2018_02_24
Site Map 2018_02_25
Site Map 2018_02_26
Site Map 2018_02_27
Site Map 2018_02_28
Site Map 2018_03_01
Site Map 2018_03_02
Site Map 2018_03_03
Site Map 2018_03_04
Site Map 2018_03_05
Site Map 2018_03_06
Site Map 2018_03_07
Site Map 2018_03_08
Site Map 2018_03_09
Site Map 2018_03_10
Site Map 2018_03_11
Site Map 2018_03_12
Site Map 2018_03_13
Site Map 2018_03_14
Site Map 2018_03_15
Site Map 2018_03_16
Site Map 2018_03_17
Site Map 2018_03_18
Site Map 2018_03_19
Site Map 2018_03_20
Site Map 2018_03_21
Site Map 2018_03_22
Site Map 2018_03_23
Site Map 2018_03_24
Site Map 2018_03_25
Site Map 2018_03_26
Site Map 2018_03_27
Site Map 2018_03_28
Site Map 2018_03_29
Site Map 2018_03_30
Site Map 2018_03_31
Site Map 2018_04_01
Site Map 2018_04_02
Site Map 2018_04_03
Site Map 2018_04_04
Site Map 2018_04_05
Site Map 2018_04_06
Site Map 2018_04_07
Site Map 2018_04_08
Site Map 2018_04_09
Site Map 2018_04_10
Site Map 2018_04_11
Site Map 2018_04_12
Site Map 2018_04_13
Site Map 2018_04_14
Site Map 2018_04_15
Site Map 2018_04_16
Site Map 2018_04_17
Site Map 2018_04_18
Site Map 2018_04_19
Site Map 2018_04_20
Site Map 2018_04_21
Site Map 2018_04_22
Site Map 2018_04_23
Site Map 2018_04_24
Site Map 2018_04_25
Site Map 2018_04_26
Site Map 2018_04_27
Site Map 2018_04_28
Site Map 2018_04_29
Site Map 2018_04_30
Site Map 2018_05_01
Site Map 2018_05_02
Site Map 2018_05_03
Site Map 2018_05_04
Site Map 2018_05_05
Site Map 2018_05_06
Site Map 2018_05_07
Site Map 2018_05_08
Site Map 2018_05_09
Site Map 2018_05_15
Site Map 2018_05_16
Site Map 2018_05_17
Site Map 2018_05_18
Site Map 2018_05_19
Site Map 2018_05_20
Site Map 2018_05_21
Site Map 2018_05_22
Site Map 2018_05_23
Site Map 2018_05_24
Site Map 2018_05_25
Site Map 2018_05_26
Site Map 2018_05_27
Site Map 2018_05_28
Site Map 2018_05_29
Site Map 2018_05_30
Site Map 2018_05_31
Site Map 2018_06_01
Site Map 2018_06_02
Site Map 2018_06_03
Site Map 2018_06_04
Site Map 2018_06_05
Site Map 2018_06_06
Site Map 2018_06_07
Site Map 2018_06_08
Site Map 2018_06_09
Site Map 2018_06_10
Site Map 2018_06_11
Site Map 2018_06_12
Site Map 2018_06_13
Site Map 2018_06_14
Site Map 2018_06_15
Site Map 2018_06_16
Site Map 2018_06_17
Site Map 2018_06_18
Site Map 2018_06_19
Site Map 2018_06_20
Site Map 2018_06_21
Site Map 2018_06_22
Site Map 2018_06_23
Site Map 2018_06_24
Site Map 2018_06_25
Site Map 2018_06_26
Site Map 2018_06_27
Site Map 2018_06_28
Site Map 2018_06_29
Site Map 2018_06_30
Site Map 2018_07_01
Site Map 2018_07_02
Site Map 2018_07_03
Site Map 2018_07_04
Site Map 2018_07_05
Site Map 2018_07_06
Site Map 2018_07_07
Site Map 2018_07_08
Site Map 2018_07_09
Site Map 2018_07_10
Site Map 2018_07_11
Site Map 2018_07_12
Site Map 2018_07_13
Site Map 2018_07_14
Site Map 2018_07_15
Site Map 2018_07_16
Site Map 2018_07_17
Site Map 2018_07_18
Site Map 2018_07_19
Site Map 2018_07_20
Site Map 2018_07_21
Site Map 2018_07_22
Site Map 2018_07_23
Site Map 2018_07_24
Site Map 2018_07_25
Site Map 2018_07_26
Site Map 2018_07_27
Site Map 2018_07_28
Site Map 2018_07_29
Site Map 2018_07_30
Site Map 2018_07_31
Site Map 2018_08_01
Site Map 2018_08_02
Site Map 2018_08_03
Site Map 2018_08_04
Site Map 2018_08_05
Site Map 2018_08_06
Site Map 2018_08_07
Site Map 2018_08_08
Site Map 2018_08_09
Site Map 2018_08_10
Site Map 2018_08_11
Site Map 2018_08_12
Site Map 2018_08_13
Site Map 2018_08_15
Site Map 2018_08_16
Site Map 2018_08_17
Site Map 2018_08_18
Site Map 2018_08_19
Site Map 2018_08_20
Site Map 2018_08_21
Site Map 2018_08_22
Site Map 2018_08_23
Site Map 2018_08_24
Site Map 2018_08_25
Site Map 2018_08_26
Site Map 2018_08_27
Site Map 2018_08_28
Site Map 2018_08_29
Site Map 2018_08_30
Site Map 2018_08_31
Site Map 2018_09_01
Site Map 2018_09_02
Site Map 2018_09_03
Site Map 2018_09_04
Site Map 2018_09_05
Site Map 2018_09_06
Site Map 2018_09_07
Site Map 2018_09_08
Site Map 2018_09_09
Site Map 2018_09_10
Site Map 2018_09_11
Site Map 2018_09_12
Site Map 2018_09_13